Triple
T22860561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stafford Motor Speedway |
E566906
|
entity |
| Predicate | hostsSpecialEvents |
P613
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stafford Motor Speedway, hostsSpecialEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsSpecialEvents Context triple: [Stafford Motor Speedway, hostsSpecialEvents, yes]
-
A.
hostsEvent
chosen
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
countryHostedEvent
Indicates that a specific country served as the host location for a particular event.
-
C.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
D.
hostedAttraction
Indicates that an entity served as the venue or location where a particular attraction, event, or feature was presented or took place.
-
E.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ec082c08190943e6cfc2e25c5cc |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.