Triple
T28020109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal highway network |
E707661
|
entity |
| Predicate | includesExpresswaySections |
P7229
|
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: [German federal highway network, includesExpresswaySections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExpresswaySections Context triple: [German federal highway network, includesExpresswaySections, yes]
-
A.
hasExpresswaySection
chosen
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
B.
openedAsExpresswaySection
Indicates that a particular section of roadway was inaugurated and began operation specifically as an expressway segment.
-
C.
hasExpresswayName
Indicates that an entity (such as a road segment or route) is associated with a specific expressway name.
-
D.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service entity.
-
E.
hasExpressLanes
Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 27, 2026, 8:09 p.m.