Triple
T23593662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal hairpin |
E582551
|
entity |
| Predicate | hasRacingLine |
P55674
|
FINISHED |
| Object | late apex |
—
|
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: late apex | Statement: [Montreal hairpin, hasRacingLine, late apex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRacingLine Context triple: [Montreal hairpin, hasRacingLine, late apex]
-
A.
hasRacingCode
Indicates that an entity is associated with a specific racing classification or identifier code.
-
B.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
C.
hasRacingSide
Indicates that an entity possesses or is associated with a side or aspect specifically dedicated to racing.
-
D.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
E.
hasRacecourseFeature
chosen
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.