Triple
T4102302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Speed |
E87967
|
entity |
| Predicate | typicalSpectatorAccess |
P31261
|
FINISHED |
| Object | pits and start line areas |
—
|
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: pits and start line areas | Statement: [World of Speed, typicalSpectatorAccess, pits and start line areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpectatorAccess Context triple: [World of Speed, typicalSpectatorAccess, pits and start line areas]
-
A.
spectatorType
Indicates the role or category of a spectator in relation to an event or activity.
-
B.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
C.
spectatorAreaType
chosen
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
D.
spectatorSport
Indicates that an activity is primarily performed for the enjoyment of an audience watching rather than for direct participation.
-
E.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd1012208190ab0980c661d6bc41 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.