Triple
T36233645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blyth Spartans A.F.C. |
E891315
|
entity |
| Predicate | famousMatchOpponent |
P18798
|
FINISHED |
| Object | Wrexham A.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: Wrexham A.F.C. | Statement: [Blyth Spartans A.F.C., famousMatchOpponent, Wrexham A.F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousMatchOpponent Context triple: [Blyth Spartans A.F.C., famousMatchOpponent, Wrexham A.F.C.]
-
A.
famousMatch
chosen
Indicates that two entities are linked by a match or pairing that is widely known or celebrated.
-
B.
finalLeagueMatchOpponent
Indicates the opposing team or player faced in an entity’s final league match.
-
C.
leagueCupFinalOpponent
Indicates that one entity is the opponent faced by another entity in the final match of a league cup competition.
-
D.
finalOpponentOf
Indicates that one entity serves as the last or ultimate opponent faced by another entity in a sequence of confrontations or competitions.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5a590d881908f186b05dc5702a4 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.