Triple
T35556859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Lakers vs. Boston Celtics |
E1027520
|
entity |
| Predicate | notableFinalsSeries |
P115592
|
FINISHED |
| Object | 1984 NBA Finals |
E375158
|
NE 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: 1984 NBA Finals | Statement: [Los Angeles Lakers vs. Boston Celtics, notableFinalsSeries, 1984 NBA Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFinalsSeries Context triple: [Los Angeles Lakers vs. Boston Celtics, notableFinalsSeries, 1984 NBA Finals]
-
A.
notablePostseasonSeries
Indicates that there exists a postseason series in which the subject played a particularly significant or memorable role in relation to the object.
-
B.
hasFinalsSeries
chosen
Indicates that there exists a specific finals series associated with or assigned to a given entity.
-
C.
conferenceFinalsSeriesResult
Indicates the outcome of a conference finals playoff series between two competitors, including which side won and by what series score.
-
D.
notableFinalSeasonChampion
Indicates that the subject is notably recognized as the champion in the final season of a competition, series, or event.
-
E.
notableGameSeries
Indicates that there exists a game series for which the subject is notably recognized or strongly associated.
- F. None of above.
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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852f774c88190ab556b740cff70f3 |
completed | June 21, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.