Triple
T9536733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe national football team |
E230036
|
entity |
| Predicate | regionalTournamentFirstAppearanceYear |
P33825
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Zimbabwe national football team, regionalTournamentFirstAppearanceYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalTournamentFirstAppearanceYear Context triple: [Zimbabwe national football team, regionalTournamentFirstAppearanceYear, 2004]
-
A.
regionalCupFirstAppearance
chosen
Indicates the first time an entity participated in a specified regional cup competition.
-
B.
firstKnownTournamentYear
Indicates the year in which a tournament was first known to have been held.
-
C.
firstKnownTournament
Indicates the earliest tournament in which the entity is known or recorded to have participated or appeared.
-
D.
firstUsedInTournament
Indicates that an entity (such as a move, strategy, or item) was used for the first time in a specific tournament.
-
E.
worldChampionshipDebut
Indicates the event or occasion on which an entity first appeared or participated in a world championship.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98ce884c8190a8b3c2dc7c73c2c9 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8:01 p.m.