Triple
T8211060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radiator Springs Racers |
E191815
|
entity |
| Predicate | usesTrackLayout |
P22148
|
FINISHED |
| Object | dual side-by-side tracks |
—
|
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: dual side-by-side tracks | Statement: [Radiator Springs Racers, usesTrackLayout, dual side-by-side tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTrackLayout Context triple: [Radiator Springs Racers, usesTrackLayout, dual side-by-side tracks]
-
A.
trackLayout
chosen
Indicates how the components or segments of a track are arranged and connected in relation to one another.
-
B.
hasCenterTrackUsage
Indicates that an entity utilizes or is assigned to a central track within a multi-track system or layout.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
-
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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dec42c819090252fe186a68d34 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.