Triple
T20525130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autobahn A12 |
E503914
|
entity |
| Predicate | hasSpeedRegime |
P140422
|
FINISHED |
| Object | German autobahn speed regulations |
—
|
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: German autobahn speed regulations | Statement: [Autobahn A12, hasSpeedRegime, German autobahn speed regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedRegime Context triple: [Autobahn A12, hasSpeedRegime, German autobahn speed regulations]
-
A.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
B.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
-
C.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
E.
hasSpeedLimitCategory
Indicates that an entity is associated with a specific category or classification of speed limit.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06504b48190b3f1defdc23a47d5 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:37 a.m.