Triple
T36873341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E12 |
E911278
|
entity |
| Predicate | routeSectionInNorway |
P186735
|
FINISHED |
| Object | Mo i Rana–Swedish border |
—
|
NE NERFINISHED |
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: Mo i Rana–Swedish border | Statement: [European route E12, routeSectionInNorway, Mo i Rana–Swedish border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSectionInNorway Context triple: [European route E12, routeSectionInNorway, Mo i Rana–Swedish border]
-
A.
directionFromOslo
Indicates the cardinal or relative direction in which one location lies when measured from Oslo.
-
B.
roadDirectionFromNorseman
Indicates the direction or path that a road takes when starting from Norseman.
-
C.
distanceFromKristiansand
Indicates the spatial distance between a given location or object and the city of Kristiansand.
-
D.
distanceFromTrondheimOnNordlandLine_km
Indicates the distance in kilometers of a location measured along the Nordland railway line from Trondheim.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- F. None of above. chosen
Provenance (4 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.