Triple
T15840563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calder Park Raceway |
E384089
|
entity |
| Predicate | roadCourseLayout |
P22148
|
FINISHED |
| Object | permanent circuit |
—
|
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: permanent circuit | Statement: [Calder Park Raceway, roadCourseLayout, permanent circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadCourseLayout Context triple: [Calder Park Raceway, roadCourseLayout, permanent circuit]
-
A.
trackLayout
chosen
Indicates how the components or segments of a track are arranged and connected in relation to one another.
-
B.
trackDesigner
Indicates that one entity is the designer or creator responsible for the layout or structure of a track associated with another entity.
-
C.
laneStructure
Indicates the structural organization and configuration of lanes within a roadway or traffic facility.
-
D.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
E.
trailOrientation
Indicates the directional alignment or facing direction of a trail relative to a reference frame or compass directions.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.