Triple
T35683832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish national road 45 |
E1031085
|
entity |
| Predicate | continuesNorthwardAs |
P139172
|
FINISHED |
| Object | important regional route |
—
|
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: important regional route | Statement: [Finnish national road 45, continuesNorthwardAs, important regional route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesNorthwardAs Context triple: [Finnish national road 45, continuesNorthwardAs, important regional route]
-
A.
northernContinuationOf
chosen
Indicates that one entity is a direct geographic or structural continuation of another entity toward the north.
-
B.
northernDirection
Indicates a spatial relationship where one entity is located to the north of another entity.
-
C.
hasContinuationNorth
Indicates that something extends, continues, or has a connected part toward the north.
-
D.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
E.
opensNorthwardTo
Indicates that one entity has an opening, entrance, or exposure that faces or leads toward the north.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:05 p.m.