Triple
T16865129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autobahn GmbH des Bundes |
E410016
|
entity |
| Predicate | appliesToRoadCategory |
P122625
|
FINISHED |
| Object | Bundesautobahn |
—
|
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: Bundesautobahn | Statement: [Autobahn GmbH des Bundes, appliesToRoadCategory, Bundesautobahn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRoadCategory Context triple: [Autobahn GmbH des Bundes, appliesToRoadCategory, Bundesautobahn]
-
A.
appliesToRoadType
chosen
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
B.
appliesToRoad
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a road.
-
C.
isRoadPass
Indicates that a particular road or route is currently passable or open for travel.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b506dd1c81909ab8006b6a1e2b7a |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.