Triple
T33771952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fångad av en stormvind |
E865405
|
entity |
| Predicate | finalScoreType |
P196515
|
FINISHED |
| Object | tie-break win over France |
—
|
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: tie-break win over France | Statement: [Fångad av en stormvind, finalScoreType, tie-break win over France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreType Context triple: [Fångad av en stormvind, finalScoreType, tie-break win over France]
-
A.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
finalSetScore
Indicates the final score achieved in a particular set within a match or game.
-
C.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
D.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
E.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
- F. None of above. chosen
Provenance (4 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 1, 2026, 1:45 a.m.