Triple
T27357462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 NBA Finals |
E685723
|
entity |
| Predicate | BullsTitlesConsecutive |
P43846
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1993 NBA Finals, BullsTitlesConsecutive, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BullsTitlesConsecutive Context triple: [1993 NBA Finals, BullsTitlesConsecutive, 3]
-
A.
BullsPlayoffRecord
Indicates the Chicago Bulls’ win–loss record in NBA playoff games for a given season or time span.
-
B.
consecutiveWinningSeasons
Indicates that an entity (such as a team or individual) has achieved winning seasons in back-to-back or uninterrupted consecutive years.
-
C.
BullsRegularSeasonRecord
Indicates the relationship that specifies the Chicago Bulls’ win–loss record for a particular NBA regular season.
-
D.
consecutiveLeagueTitlesPeriod
Indicates a time span during which a team or entity wins league titles in consecutive seasons without interruption.
-
E.
consecutiveLeagueTitles
chosen
Indicates that one entity has won league titles in successive seasons without interruption.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:52 a.m.