Triple
T31932761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Food City 500 |
E815297
|
entity |
| Predicate | hostTrackConfiguration |
P122335
|
FINISHED |
| Object | four-turn oval |
—
|
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: four-turn oval | Statement: [Food City 500, hostTrackConfiguration, four-turn oval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTrackConfiguration Context triple: [Food City 500, hostTrackConfiguration, four-turn oval]
-
A.
hasTrackFacility
Indicates that one entity provides or includes a track facility (such as a running or racing track) available for use by another entity.
-
B.
currentTrackConfiguration
chosen
Indicates the specific arrangement or layout of tracks that is currently active or in use.
-
C.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
-
D.
isHotspotTrackOf
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
E.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2311c7481909fdfa0067f3b5082 |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:04 a.m.