Triple
T15068299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 NBA Finals |
E379810
|
entity |
| Predicate | Game 6 MagicJohnsonAssists |
P61570
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [1980 NBA Finals, Game 6 MagicJohnsonAssists, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Game 6 MagicJohnsonAssists Context triple: [1980 NBA Finals, Game 6 MagicJohnsonAssists, 7]
-
A.
numberOfTimesAwardedNBA Sixth Man of the Year Award
Indicates how many times an individual has received the NBA Sixth Man of the Year Award.
-
B.
assistsInNBA
Indicates a relationship where one entity provides an assist to another entity during an NBA game or within the context of NBA play.
-
C.
game7NotablePlay
Indicates that a specific play is recognized as particularly significant or memorable within the context of a Game 7.
-
D.
MVPAssists
Indicates that one entity, recognized as the most valuable player (MVP), provides assistance or support to another entity in achieving a goal or outcome.
-
E.
recordAssistsInThatGame
chosen
Indicates that one entity achieved the highest number of assists in a particular game.
- 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.