Triple
T30985940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Volta national football team |
E789525
|
entity |
| Predicate | countryNameChangeFrom |
P33813
|
FINISHED |
| Object | Upper Volta |
—
|
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: Upper Volta | Statement: [Upper Volta national football team, countryNameChangeFrom, Upper Volta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryNameChangeFrom Context triple: [Upper Volta national football team, countryNameChangeFrom, Upper Volta]
-
A.
laterNameOfCountry
Indicates that the referenced entity is a later or subsequent name adopted by a country that previously had a different name.
-
B.
renamingCountry
Indicates that one country is changing its official name to a new one.
-
C.
previousNameOfCountry
chosen
Indicates that one country name was formerly used as the official name of another country.
-
D.
originalCountryNowKnownAs
Indicates that a country previously known by one name is now recognized under a different current country name.
-
E.
existedBeforeCountryNameChange
Indicates that an entity existed prior to the point in time when a country changed its official name.
- 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_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 29, 2026, 8:56 p.m.