Triple
T21784760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lummen |
E537805
|
entity |
| Predicate | hasRoadInfrastructureFeature |
P1777
|
FINISHED |
| Object | Lummen junction |
—
|
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: Lummen junction | Statement: [Lummen, hasRoadInfrastructureFeature, Lummen junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadInfrastructureFeature Context triple: [Lummen, hasRoadInfrastructureFeature, Lummen junction]
-
A.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
B.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
C.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
D.
hasCarriagewayFacilities
Indicates that specific facilities, features, or infrastructure elements are present on or along a carriageway.
-
E.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f04630f4f08190910b9e499a4249ca |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.