Triple
T16956002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of America Roval 400 |
E411302
|
entity |
| Predicate | usesInfieldRoadCourse |
P125378
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bank of America Roval 400, usesInfieldRoadCourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInfieldRoadCourse Context triple: [Bank of America Roval 400, usesInfieldRoadCourse, true]
-
A.
infieldRoadCourseLength
Indicates the length of the road course section located within the infield area of a racing circuit.
-
B.
hasIndoorTrack
Indicates that a place or facility includes an indoor track as one of its features or amenities.
-
C.
containsChampionshipCourse
Indicates that an entity includes or features a golf course that meets recognized championship-level standards.
-
D.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
E.
infieldSurface
Indicates that one entity serves as the playing surface material or type for the infield area of another entity (such as a sports field or stadium).
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01bb700819082a441c124be3cb6 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.