Triple
T30521527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldSSP |
E776703
|
entity |
| Predicate | pitLaneRules |
P130333
|
FINISHED |
| Object | regulated pit lane procedures |
—
|
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: regulated pit lane procedures | Statement: [WorldSSP, pitLaneRules, regulated pit lane procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitLaneRules Context triple: [WorldSSP, pitLaneRules, regulated pit lane procedures]
-
A.
pitStopRules
chosen
Indicates the rules or conditions governing when and how pit stops must be performed in a race or similar process.
-
B.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
C.
pitLaneSharedWith
Indicates that two racing pit lanes are configured so that they are used jointly or overlap in access or operation.
-
D.
safetyCarRegulations
Indicates regulations governing when and how a safety car is deployed and managed during an event or process.
-
E.
lapsUnderCaution
Indicates that the laps occurred while the event was under a caution or safety period rather than normal racing 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6880b4a788190b7031f48ee4daf3a |
completed | May 2, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:17 p.m.