Triple
T480590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigeria national football team |
E9157
|
entity |
| Predicate | afconThirdPlace |
P12516
|
FINISHED |
| Object | 1976 |
—
|
LITERAL 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: 1976 | Statement: [Nigeria national football team, afconThirdPlace, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afconThirdPlace Context triple: [Nigeria national football team, afconThirdPlace, 1976]
-
A.
thirdPlaceTeam
chosen
Indicates that a team finished in third place in a competition, league, or ranking.
-
B.
thirdPlacePlayoff
Indicates a match or contest held to determine which participant finishes in third place, typically between the losers of the semifinals.
-
C.
thirdPlacePrize
Indicates that an entity receives or is associated with the prize awarded for finishing in third place in a competition or ranking.
-
D.
conferenceChampionAFC
Indicates that a team has won the American Football Conference (AFC) championship for a given season.
-
E.
thirdInMedalTable
Indicates that an entity finished in third place in a ranking of medal counts (a medal table), typically in a competition or multi-sport event.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f058ebe48190aaa0a829b21f75fa |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.