Triple
T19460217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 of the 2016 World Series |
E486846
|
entity |
| Predicate | seriesStatusEnteringGame |
P136003
|
FINISHED |
| Object | series tied 3–3 |
—
|
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: series tied 3–3 | Statement: [Game 7 of the 2016 World Series, seriesStatusEnteringGame, series tied 3–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesStatusEnteringGame Context triple: [Game 7 of the 2016 World Series, seriesStatusEnteringGame, series tied 3–3]
-
A.
ramsRecordEnteringGame
Indicates the performance record (such as wins and losses) that the Rams team holds at the time they enter a particular game.
-
B.
visitorRecordEnteringGame
Indicates that a record is being created or logged for a visitor who is entering or starting a game.
-
C.
CentreRecordEnteringGame
Indicates that a center player is entering the game and this event is being recorded.
-
D.
stateGame6
Indicates that an entity is in the specific condition or configuration labeled as "game6" within a set of game-related states.
-
E.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.