Triple
T25766447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Raceway |
E648895
|
entity |
| Predicate | infieldRoadCourse |
P125378
|
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: [Richmond Raceway, infieldRoadCourse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infieldRoadCourse Context triple: [Richmond Raceway, infieldRoadCourse, yes]
-
A.
infieldRoadCourseLength
Indicates the length of the road course section located within the infield area of a racing circuit.
-
B.
usesInfieldRoadCourse
chosen
Indicates that something incorporates or operates on an infield road course as part of its route or layout.
-
C.
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).
-
D.
infieldUse
Indicates that something is used or applied within a specific field, area, or domain.
-
E.
hasIndoorTrack
Indicates that a place or facility includes an indoor track as one of its features or amenities.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf3b14c8190b246bfb191815fd5 |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:10 a.m.