Triple
T27464467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunaudières Straight |
E693138
|
entity |
| Predicate | maximumSpeedsExceeded |
P170648
|
FINISHED |
| Object | 400 km/h |
—
|
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: 400 km/h | Statement: [Hunaudières Straight, maximumSpeedsExceeded, 400 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedsExceeded Context triple: [Hunaudières Straight, maximumSpeedsExceeded, 400 km/h]
-
A.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
B.
previousSpeedLimit
Indicates that a specified speed limit was in effect immediately before the current or another referenced speed limit.
-
C.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
speedSupervision
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- F. None of above. chosen
Provenance (4 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 12:51 p.m.