Triple
T8700762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group F (2018 FIFA World Cup) |
E206523
|
entity |
| Predicate | tiebreakerCriterion |
P6631
|
FINISHED |
| Object | goal difference |
—
|
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: goal difference | Statement: [Group F (2018 FIFA World Cup), tiebreakerCriterion, goal difference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiebreakerCriterion Context triple: [Group F (2018 FIFA World Cup), tiebreakerCriterion, goal difference]
-
A.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
-
C.
decisiveScoreType
Indicates the type or category of score used to determine a decisive outcome in a comparison or decision process.
-
D.
determinesChampionBy
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
E.
decisivePenaltyScorer
Indicates that an entity scores a crucial penalty that decisively determines the outcome of a match or competition.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b27bd48190a5f76111ee657553 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.