Triple
T22049234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil vs Germany (2014 FIFA World Cup) |
E544838
|
entity |
| Predicate | finalScoreline |
P2625
|
FINISHED |
| Object | Brazil 1–7 Germany |
—
|
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: Brazil 1–7 Germany | Statement: [Brazil vs Germany (2014 FIFA World Cup), finalScoreline, Brazil 1–7 Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreline Context triple: [Brazil vs Germany (2014 FIFA World Cup), finalScoreline, Brazil 1–7 Germany]
-
A.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalOfficialMatch
Indicates that a given match is the last officially recognized contest or game in a defined series, season, tournament, or career.
-
D.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
E.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283191e48190b4ddc84138243327 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.