Triple
T21629730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 FIFA World Cup final |
E533796
|
entity |
| Predicate | resultAfter90Minutes |
P37978
|
FINISHED |
| Object | 0–0 |
—
|
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: 0–0 | Statement: [2010 FIFA World Cup final, resultAfter90Minutes, 0–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAfter90Minutes Context triple: [2010 FIFA World Cup final, resultAfter90Minutes, 0–0]
-
A.
finalScore90Minutes
chosen
Indicates the final score of a match after the standard 90 minutes of regular playing time, excluding any extra time or penalty shootouts.
-
B.
endTimeNinthCircuit
Indicates the time at which an event, action, or process concludes within the context or jurisdiction of the Ninth Circuit.
-
C.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
D.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
E.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5215ae3c81909e6dedba23822970 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.