Triple
T32827679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 FIFA World Cup opening match |
E839595
|
entity |
| Predicate | FIFATournamentHost |
P70551
|
FINISHED |
| Object | Brazil |
—
|
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: Brazil | Statement: [2014 FIFA World Cup opening match, FIFATournamentHost, Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIFATournamentHost Context triple: [2014 FIFA World Cup opening match, FIFATournamentHost, Brazil]
-
A.
FIFATournament
Indicates a relationship where an entity is recognized as a tournament organized, sanctioned, or officially associated with FIFA.
-
B.
fifaWorldCupOrganiser
Indicates that the subject is the organizing body responsible for staging and managing the specified FIFA World Cup tournament.
-
C.
worldCupHost
chosen
Indicates that one entity serves as the host country or location for a particular FIFA World Cup tournament.
-
D.
fifaWorldCupMatchesHosted
Indicates that an entity (typically a country, city, or stadium) has hosted one or more official FIFA World Cup matches.
-
E.
WorldCupOrganizer
Indicates the entity that is responsible for organizing, managing, and overseeing the World Cup tournament.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.