Triple
T30208974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shots |
E768015
|
entity |
| Predicate | predecessorClubNickname |
P186465
|
FINISHED |
| Object | Aldershot F.C. |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Aldershot F.C. | Statement: [The Shots, predecessorClubNickname, Aldershot F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorClubNickname Context triple: [The Shots, predecessorClubNickname, Aldershot F.C.]
-
A.
predecessorClubAssociation
Indicates that one club or team previously existed in place of, or was succeeded by, another club or team in an organizational or historical lineage.
-
B.
nicknameOfClubFormerName
Indicates that a given nickname was used for a club when it had a former or previous official name.
-
C.
clubFormerName
Indicates that a sports club previously operated under a different official name.
-
D.
mostSuccessfulClubFormerName
Indicates that an entity was previously known by a different name during the period when it held the status of most successful club.
-
E.
successorClubPlaysIn
Indicates that the club which succeeds another club participates in a specified league or competition.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 29, 2026, 7:32 p.m.