Triple
T24646082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 NBA Finals |
E610112
|
entity |
| Predicate | historicRivalry |
P22384
|
FINISHED |
| Object | Los Angeles Lakers–Boston Celtics rivalry |
—
|
NE NERFINISHED |
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: Los Angeles Lakers–Boston Celtics rivalry | Statement: [1985 NBA Finals, historicRivalry, Los Angeles Lakers–Boston Celtics rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicRivalry Context triple: [1985 NBA Finals, historicRivalry, Los Angeles Lakers–Boston Celtics rivalry]
-
A.
hasHistoricRivalry
chosen
Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
-
B.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
C.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
D.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
E.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.