Triple
T27466620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Diamonds |
E693191
|
entity |
| Predicate | clubPredecessor |
P137706
|
FINISHED |
| Object | Airdrieonians F.C. (1878–2002) |
—
|
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: Airdrieonians F.C. (1878–2002) | Statement: [The Diamonds, clubPredecessor, Airdrieonians F.C. (1878–2002)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubPredecessor Context triple: [The Diamonds, clubPredecessor, Airdrieonians F.C. (1878–2002)]
-
A.
clubPredecessorOf
chosen
Indicates that one club existed earlier and was replaced or succeeded by another club in an organizational or historical sequence.
-
B.
leaguePredecessor
Indicates that one league existed before and was replaced or succeeded by another league in an organizational or historical sequence.
-
C.
clubFormerName
Indicates that a sports club previously operated under a different official name.
-
D.
predecessorFranchise
Indicates that one franchise directly precedes and is succeeded by another franchise in a series or lineage.
-
E.
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.
- F. None of above.
Provenance (3 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfd746481908fead735f9ccd021 |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:52 p.m.