Triple
T5708818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Motor Speedway |
E125852
|
entity |
| Predicate | The Dirt Track at CharlotteInstanceOf |
P65716
|
FINISHED |
| Object | dirt oval track |
—
|
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: dirt oval track | Statement: [Charlotte Motor Speedway, The Dirt Track at CharlotteInstanceOf, dirt oval track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: The Dirt Track at CharlotteInstanceOf Context triple: [Charlotte Motor Speedway, The Dirt Track at CharlotteInstanceOf, dirt oval track]
-
A.
hasMotorRacingCircuit
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
-
B.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
C.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
hasIndoorTrack
Indicates that a place or facility includes an indoor track as one of its features or amenities.
-
E.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248ab6a88190be17bdc32c36e5cb |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c023dfec6881909ee6189b874b4348 |
completed | March 22, 2026, 5:16 p.m. |
Created at: March 22, 2026, 3:46 p.m.