Triple
T23950181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Bulls vs Detroit Pistons |
E603023
|
entity |
| Predicate | rivalryPeakYears |
P73130
|
FINISHED |
| Object | 1988–1991 |
—
|
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: 1988–1991 | Statement: [Chicago Bulls vs Detroit Pistons, rivalryPeakYears, 1988–1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryPeakYears Context triple: [Chicago Bulls vs Detroit Pistons, rivalryPeakYears, 1988–1991]
-
A.
rivalryPeriod
chosen
Indicates the time span during which two entities are engaged in an ongoing rivalry or competitive relationship.
-
B.
rivalryStartPeriod
Indicates the time period or point at which a rivalry between entities begins.
-
C.
rivalryBecameProminentAfter
Indicates that a rivalry between entities became notably more intense, visible, or significant after a specified time or event.
-
D.
activeYearsPeak
Indicates the span of years during which an entity was at the height of its activity or prominence.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:19 p.m.