Triple
T33756440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 World Indoor Championships in Athletics |
E864990
|
entity |
| Predicate | hostCityStateOrRegion |
P28660
|
FINISHED |
| Object | Indiana |
—
|
NE NERFINISHED |
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: Indiana | Statement: [1987 World Indoor Championships in Athletics, hostCityStateOrRegion, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityStateOrRegion Context triple: [1987 World Indoor Championships in Athletics, hostCityStateOrRegion, Indiana]
-
A.
hostCityRegion
chosen
Indicates the city or broader region that serves as the host location for a specified event or entity.
-
B.
hostCityLocatedOn
Indicates that the city serving as a host (e.g., of an event) is geographically situated on or along a specified physical feature or area (such as a river, coast, or region).
-
C.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
D.
stationCity
Indicates that a station is located in or associated with a particular city.
-
E.
hostCityOfEventParticipatedIn
Indicates that a city is the location where a particular event took place in which an entity participated.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:45 a.m.