Triple
T23013564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolex Sports Car Series |
E572968
|
entity |
| Predicate | pitStopRule |
P130333
|
FINISHED |
| Object | controlled pit stops under caution |
—
|
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: controlled pit stops under caution | Statement: [Rolex Sports Car Series, pitStopRule, controlled pit stops under caution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitStopRule Context triple: [Rolex Sports Car Series, pitStopRule, controlled pit stops under caution]
-
A.
pitStopRules
chosen
Indicates the rules or conditions governing when and how pit stops must be performed in a race or similar process.
-
B.
pitStopsRequired
Indicates that a process, journey, or operation necessitates one or more scheduled pit stops to be completed.
-
C.
penaltyRules
Indicates the rules or conditions under which penalties are defined, applied, or enforced in a given context.
-
D.
lapsUnderCaution
Indicates that the laps occurred while the event was under a caution or safety period rather than normal racing conditions.
-
E.
roundOfStoppage
Indicates the specific round in which a contest, match, or event was stopped or ended prematurely.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.