Triple
T1601470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elam Ending |
E34401
|
entity |
| Predicate | determinesWinnerBy |
P3221
|
FINISHED |
| Object | first team to reach target score |
—
|
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: first team to reach target score | Statement: [Elam Ending, determinesWinnerBy, first team to reach target score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinesWinnerBy Context triple: [Elam Ending, determinesWinnerBy, first team to reach target score]
-
A.
determinesChampionBy
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
B.
decidingGameWinner
chosen
Indicates that an event, action, or process determines which participant is the winner of a game.
-
C.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
D.
positionOfWinner
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
E.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.