Triple
T16778646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 NBA Finals |
E407796
|
entity |
| Predicate | Game1Result |
P61386
|
FINISHED |
| Object | Miami Heat 92–84 Dallas Mavericks |
—
|
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: Miami Heat 92–84 Dallas Mavericks | Statement: [2011 NBA Finals, Game1Result, Miami Heat 92–84 Dallas Mavericks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Game1Result Context triple: [2011 NBA Finals, Game1Result, Miami Heat 92–84 Dallas Mavericks]
-
A.
game1Winner
Indicates which participant or team won the first game in a series or match.
-
B.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
C.
finalGameScoreGame1
chosen
Indicates the final score recorded for the first game in a series or set of games.
-
D.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
E.
game3Winner
Indicates that the referenced entity is the winner of the third game in a series or sequence of games.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.