Triple
T23955372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 WNBA Finals |
E603772
|
entity |
| Predicate | loserQualifiedAs |
P13508
|
FINISHED |
| Object | WNBA Finals runner-up |
—
|
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: WNBA Finals runner-up | Statement: [2001 WNBA Finals, loserQualifiedAs, WNBA Finals runner-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loserQualifiedAs Context triple: [2001 WNBA Finals, loserQualifiedAs, WNBA Finals runner-up]
-
A.
loserStatus
chosen
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
B.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
-
C.
loserReceives
Indicates that the entity who loses in a contest, game, or comparison is the one that receives a specified item, outcome, or consequence.
-
D.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
-
E.
winnerQualifiedFor
Indicates that the entity identified as the winner has earned or met the conditions required to qualify for a subsequent stage, event, or status.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d616ec81908c796894f40f3015 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.