Triple
T17202579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autobahn A4 |
E417513
|
entity |
| Predicate | partOfTransEuropeanNetwork |
P65888
|
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 A4, partOfTransEuropeanNetwork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTransEuropeanNetwork Context triple: [Autobahn A4, partOfTransEuropeanNetwork, yes]
-
A.
hasEuropeanRoute
chosen
Indicates that a road or segment is designated as part of a specific European route within the trans-European road network.
-
B.
hasEuroregion
Indicates a relationship where a geographic or administrative entity is part of, or associated with, a specific Euroregion.
-
C.
connectsToInternationalCorridor
Indicates that an entity has a direct linkage or access to an international transportation or trade corridor.
-
D.
partOfTransitSystem
Indicates that something is a component or segment within a larger transit or transportation system.
-
E.
transportNetworkPartOf
Indicates that one transport network is a component or subdivision of a larger, encompassing transport network.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db11fc881908291bf29cc740e09 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.