Triple
T21814973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NBA Finals |
E538581
|
entity |
| Predicate | runnerUpRecordEnteringFinals |
P145761
|
FINISHED |
| Object | 58–24 |
—
|
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: 58–24 | Statement: [1991 NBA Finals, runnerUpRecordEnteringFinals, 58–24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpRecordEnteringFinals Context triple: [1991 NBA Finals, runnerUpRecordEnteringFinals, 58–24]
-
A.
runnerUpUndefeatedEnteringFinal
Indicates that an entity finished as runner-up in a competition despite having been undefeated up to the final match or round.
-
B.
runnerUpFinalFourCount
Indicates the number of times an entity has finished as the runner-up in a Final Four stage of a competition or tournament.
-
C.
runnerUpWins
Indicates that an entity finishes in second place in a competition or ranking and receives the corresponding runner-up victory or award.
-
D.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
E.
playedInFinals
Indicates that an entity participated as a competitor or player in the final round of a competition or tournament.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.