Triple
T17755099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autobahn A1 |
E443210
|
entity |
| Predicate | hasSpeedLimitFreeSections |
P36052
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Autobahn A1, hasSpeedLimitFreeSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedLimitFreeSections Context triple: [Autobahn A1, hasSpeedLimitFreeSections, yes]
-
A.
hasNoGeneralSpeedLimit
Indicates that there is no legally enforced general maximum speed limit for travel on the relevant road or in the specified area.
-
B.
hasUnrestrictedSpeedSection
chosen
Indicates that a route or roadway segment includes a section where no specific maximum speed limit is imposed.
-
C.
hasSectionWithSpeedLimit
Indicates that an entity includes a segment or portion where a specific speed limit is in effect.
-
D.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
E.
hasFreeRoads
Indicates that an entity provides or is associated with roads that can be used without paying tolls or fees.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841e7050819083a4e638ca7484f7 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.