Triple
T15068295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 NBA Finals |
E379810
|
entity |
| Predicate | Game 6 score |
P38567
|
FINISHED |
| Object | Los Angeles Lakers 123 – Philadelphia 76ers 107 |
—
|
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: Los Angeles Lakers 123 – Philadelphia 76ers 107 | Statement: [1980 NBA Finals, Game 6 score, Los Angeles Lakers 123 – Philadelphia 76ers 107]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Game 6 score Context triple: [1980 NBA Finals, Game 6 score, Los Angeles Lakers 123 – Philadelphia 76ers 107]
-
A.
game6FinalScore
chosen
Indicates the final score achieved in the sixth game of a series or sequence of games.
-
B.
game7Score
Indicates the final score or outcome of a decisive seventh game in a series between competitors.
-
C.
game6Winner
Indicates which participant or team won game 6 in a series or sequence of games.
-
D.
game5FinalScore
Indicates the final score outcome of a specific game (game 5) in a series or match.
-
E.
WorldSeriesGame6ErrorBy
Indicates that a specific error committed in Game 6 of the World Series is attributed to a particular player or fielder.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeebc7e48190a86b4f0afe8844bb |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.