Triple
T36873342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E12 |
E911278
|
entity |
| Predicate | routeSectionInSweden |
P187110
|
FINISHED |
| Object | Swedish border–Umeå |
—
|
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: Swedish border–Umeå | Statement: [European route E12, routeSectionInSweden, Swedish border–Umeå]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSectionInSweden Context triple: [European route E12, routeSectionInSweden, Swedish border–Umeå]
-
A.
routeSectionInNorway
Indicates that a specific route section is located within the geographical boundaries of Norway.
-
B.
distanceFromStockholmCityCentre
Indicates the measured distance between a given location and the center of Stockholm city.
-
C.
streetSectionOf
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
D.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
E.
nearCityOnSwedishSide
Indicates that one entity is located close to a specified city that lies on the Swedish side of a border or boundary.
- 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_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.