Triple
T29990191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 MLB All-Star Game |
E761851
|
entity |
| Predicate | hostCityPreviousYear |
P27045
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [2019 MLB All-Star Game, hostCityPreviousYear, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityPreviousYear Context triple: [2019 MLB All-Star Game, hostCityPreviousYear, 1997]
-
A.
previousHostCity
chosen
Indicates that one city served as the immediately preceding host city relative to another in a sequence of hosting events.
-
B.
hostCityPreviousOlympicsInCity
Indicates that the city served as the host city for a previous edition of the Olympic Games held in that same city.
-
C.
hostCityPreviouslyHosted
Indicates that the city currently hosting an event has also hosted that same event in one or more previous editions.
-
D.
hostCityPreviousTimeArena
Indicates that a city previously served as the host location for an event held in a particular arena.
-
E.
hostCityPreviousWinterGames
Indicates that the subject city served as the host city for the immediately preceding edition of the Winter Games relative to the event in question.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:38 p.m.