Triple
T22049239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil vs Germany (2014 FIFA World Cup) |
E544838
|
entity |
| Predicate | MiroslavKloseWorldCupGoalsAfterMatch |
P43243
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Brazil vs Germany (2014 FIFA World Cup), MiroslavKloseWorldCupGoalsAfterMatch, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MiroslavKloseWorldCupGoalsAfterMatch Context triple: [Brazil vs Germany (2014 FIFA World Cup), MiroslavKloseWorldCupGoalsAfterMatch, 16]
-
A.
worldCupGoals
chosen
Indicates the number of goals an entity scored in World Cup matches.
-
B.
FIFAWorldCupGoalsRank
Indicates the ranking of entities based on the number of goals they have scored in FIFA World Cup competitions.
-
C.
scoredGoalsInFinalOf
Indicates that one entity scored one or more goals in the final match of a specified competition or event.
-
D.
notableWorldCupFinish
Indicates that an entity achieved a significant or distinguished placement or result in a FIFA World Cup tournament.
-
E.
worldCupFinalScore
Indicates the final score outcome of a FIFA World Cup match, typically specifying the number of goals each team scored by the end of the final game.
- 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.