Triple
T23193900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IndyCar Series street circuit races |
E579821
|
entity |
| Predicate | spectatorEnvironment |
P151304
|
FINISHED |
| Object | urban city center |
—
|
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: urban city center | Statement: [IndyCar Series street circuit races, spectatorEnvironment, urban city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorEnvironment Context triple: [IndyCar Series street circuit races, spectatorEnvironment, urban city center]
-
A.
spectatorUse
Indicates that an entity observes or experiences an event, activity, or object without directly participating in or interacting with it.
-
B.
spectatorType
Indicates the role or category of a spectator in relation to an event or activity.
-
C.
spectatorAreaType
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
D.
spectatorAppeal
Indicates that an action, event, or entity is appealing, entertaining, or attractive to spectators or an audience.
-
E.
spectatorSport
Indicates that an activity is primarily performed for the enjoyment of an audience watching rather than for direct participation.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd971d08190a132d24094e0c37b |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:06 p.m.