Triple
T5635135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1989–90 NBA championship |
E147928
|
entity |
| Predicate | consecutiveTitleNumber |
P64720
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1989–90 NBA championship, consecutiveTitleNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecutiveTitleNumber Context triple: [1989–90 NBA championship, consecutiveTitleNumber, 2]
-
A.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
B.
hasSequelNumber
Indicates that an entity is followed by another work in a series identified by a specific sequential number.
-
C.
isConsecutiveTitleGameAppearance
Indicates that an entity’s appearance in a title game occurs in back-to-back seasons or events without interruption.
-
D.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
E.
consecutiveStartsRank
Indicates that one entity’s starting position in an ordered sequence immediately follows another entity’s starting position, with no gap between them.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226286208190b6ccf036cc09fe82 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.