Triple
T6803736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IndyCar Grand Prix |
E156248
|
entity |
| Predicate | mainEventAtVenue |
P49138
|
FINISHED |
| Object | Indianapolis Motor Speedway road course events |
—
|
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: Indianapolis Motor Speedway road course events | Statement: [IndyCar Grand Prix, mainEventAtVenue, Indianapolis Motor Speedway road course events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventAtVenue Context triple: [IndyCar Grand Prix, mainEventAtVenue, Indianapolis Motor Speedway road course events]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
mainEventFor
chosen
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
C.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
D.
mainVenueOpened
Indicates that the primary venue associated with an event or organization has begun operations or officially opened.
-
E.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e8d7888190a837620967a150e3 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.