Triple
T29710454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany vs Sweden (2018 FIFA World Cup) |
E751763
|
entity |
| Predicate | decisiveGoalType |
P72446
|
FINISHED |
| Object | free-kick |
—
|
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: free-kick | Statement: [Germany vs Sweden (2018 FIFA World Cup), decisiveGoalType, free-kick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveGoalType Context triple: [Germany vs Sweden (2018 FIFA World Cup), decisiveGoalType, free-kick]
-
A.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
B.
decisiveGoalGame
Indicates that a game contains a goal or scoring event that definitively determines the winner or final outcome.
-
C.
goalType
chosen
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decisive
Indicates that one entity makes a conclusive choice or determination that resolves a situation or outcome between entities.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 7:30 p.m.