Triple
T23432527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo Speedway |
E563370
|
entity |
| Predicate | hasPavedPitRoad |
P78947
|
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: [Toledo Speedway, hasPavedPitRoad, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPavedPitRoad Context triple: [Toledo Speedway, hasPavedPitRoad, yes]
-
A.
hasPitLane
chosen
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
B.
hasRacingSide
Indicates that an entity possesses or is associated with a side or aspect specifically dedicated to racing.
-
C.
hasMotorRacingCircuit
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
-
D.
hasOffRoadSections
Indicates that a route, path, or roadway includes segments that are not on standard paved or main roads, such as trails, dirt tracks, or other off-road portions.
-
E.
usesInfieldRoadCourse
Indicates that something incorporates or operates on an infield road course as part of its route or layout.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d920548190904f80c7c40cba06 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.