Triple
T30208975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shots |
E768015
|
entity |
| Predicate | associatedWithPredecessorClub |
P118510
|
FINISHED |
| Object | Aldershot F.C. |
E213220
|
NE FINISHED |
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, associatedWithPredecessorClub, Aldershot F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPredecessorClub Context triple: [The Shots, associatedWithPredecessorClub, Aldershot F.C.]
-
A.
associatedClubPredecessorState
Indicates that a club is linked to a predecessor entity that existed in an earlier state or form of the organization.
-
B.
predecessorClubAssociation
chosen
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.
-
C.
hasSuccessorClubName
Indicates that one club’s name is followed or replaced by another club’s name, typically due to succession or rebranding.
-
D.
associatedWithFormerClubName
Indicates a relationship where an entity is linked to the previous or former name of a club.
-
E.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
- F. None of above.
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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a278925c79881908688188ed32a4734 |
completed | June 9, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:32 p.m.