Triple
T1167276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1914 World Series |
E24826
|
entity |
| Predicate | loserGames |
P15131
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [1914 World Series, loserGames, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loserGames Context triple: [1914 World Series, loserGames, 0]
-
A.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
-
B.
gamesLostBy
chosen
Indicates the number of games that one entity has been defeated in by another entity.
-
C.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
D.
loserPoints
Indicates the number of points awarded to or accumulated by the losing side in a competitive event or comparison.
-
E.
losingLeague
Indicates that a league is in a losing or disadvantaged position, such as having an overall negative performance or being behind its competitors.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccd75048190b8ce88237c1a748b |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.