Triple
T13101362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 Patrick Division Finals |
E310725
|
entity |
| Predicate | loserSeriesRecord |
P50813
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [1991 Patrick Division Finals, loserSeriesRecord, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loserSeriesRecord Context triple: [1991 Patrick Division Finals, loserSeriesRecord, 1]
-
A.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
-
B.
loserLeague
Indicates that an entity participates in or belongs to a league or competition specifically designated for losers or last-place finishers.
-
C.
loserGamesWon
chosen
Indicates the number of games won by the losing participant in a match or contest.
-
D.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
E.
decidingSeriesLoser
Indicates that one entity is the loser in a game or match that determines the outcome of a series between 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981515d488190908d3cca1b84a42d |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.