Triple
T13288411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Race |
E316500
|
entity |
| Predicate | pitStops |
P44365
|
FINISHED |
| Object | multiple mandatory pit 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: multiple mandatory pit stops | Statement: [The Great Race, pitStops, multiple mandatory pit stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitStops Context triple: [The Great Race, pitStops, multiple mandatory pit stops]
-
A.
pitStopsRequired
chosen
Indicates that a process, journey, or operation necessitates one or more scheduled pit stops to be completed.
-
B.
trailStopOn
Indicates that one entity stops or terminates at the endpoint of a trail or path associated with another entity.
-
C.
roundOfStoppage
Indicates the specific round in which a contest, match, or event was stopped or ended prematurely.
-
D.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
E.
safetyCarPeriods
Indicates periods during an event when a safety car is deployed, affecting normal progression or conditions.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.