Triple
T17654594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Grand Prix |
E429586
|
entity |
| Predicate | pitStopStrategy |
P44365
|
FINISHED |
| Object | typically one or two stops |
—
|
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: typically one or two stops | Statement: [Canadian Grand Prix, pitStopStrategy, typically one or two stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitStopStrategy Context triple: [Canadian Grand Prix, pitStopStrategy, typically one or two stops]
-
A.
pitStopsRequired
chosen
Indicates that a process, journey, or operation necessitates one or more scheduled pit stops to be completed.
-
B.
roundOfStoppage
Indicates the specific round in which a contest, match, or event was stopped or ended prematurely.
-
C.
trailStopOn
Indicates that one entity stops or terminates at the endpoint of a trail or path associated with another entity.
-
D.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
-
E.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3fc6e8819080098a3cd0183811 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.