Triple
T30985942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Volta national football team |
E789525
|
entity |
| Predicate | fifaCodeChangedTo |
P88608
|
FINISHED |
| Object | BFA |
—
|
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: BFA | Statement: [Upper Volta national football team, fifaCodeChangedTo, BFA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifaCodeChangedTo Context triple: [Upper Volta national football team, fifaCodeChangedTo, BFA]
-
A.
fifaCodePreviously
chosen
Indicates that an entity previously had a specific FIFA code before it was changed or replaced.
-
B.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
C.
fifaRecognized
Indicates that an organization, competition, or entity is officially recognized or sanctioned by FIFA as meeting its standards or falling under its authority.
-
D.
fifaCodeStatus
Indicates the status or condition of an entity’s FIFA-assigned code, such as whether it is active, valid, or otherwise classified.
-
E.
fifaApproved
Indicates that something has been officially recognized, certified, or sanctioned by FIFA according to its standards or regulations.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.