Triple
T3507002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 NBA Finals |
E74099
|
entity |
| Predicate | seriesOutcomeAfterSixGames |
P48388
|
FINISHED |
| Object | Portland Trail Blazers won 4–2 |
—
|
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: Portland Trail Blazers won 4–2 | Statement: [1977 NBA Finals, seriesOutcomeAfterSixGames, Portland Trail Blazers won 4–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesOutcomeAfterSixGames Context triple: [1977 NBA Finals, seriesOutcomeAfterSixGames, Portland Trail Blazers won 4–2]
-
A.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
B.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
C.
subsequentOutcomeForWinner
Indicates that the predicate links a winner to an outcome or event that occurs to or for them after their initial victory.
-
D.
homeTeamForGames6And7
Indicates which team is designated as the home team for games 6 and 7 in a series or schedule.
-
E.
game6Winner
Indicates which participant or team won game 6 in a series or sequence of games.
- F. None of above. chosen
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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf52bd8819085a2ac5f48cc5c68 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.