Triple
T21366394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A111 motorway |
E526925
|
entity |
| Predicate | hasSpeedLimitPolicy |
P144000
|
FINISHED |
| Object | advisory speed 130 km/h on German autobahns |
—
|
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: advisory speed 130 km/h on German autobahns | Statement: [A111 motorway, hasSpeedLimitPolicy, advisory speed 130 km/h on German autobahns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedLimitPolicy Context triple: [A111 motorway, hasSpeedLimitPolicy, advisory speed 130 km/h on German autobahns]
-
A.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
B.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
-
C.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
D.
hasSectionWithSpeedLimit
Indicates that an entity includes a segment or portion where a specific speed limit is in effect.
-
E.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06fbe108190a07a46824b96a963 |
completed | April 22, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:09 p.m.