Triple
T36873381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish national road 4 |
E911279
|
entity |
| Predicate | hasMotorwaySection |
P7229
|
FINISHED |
| Object | Helsinki–Lahti |
—
|
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: Helsinki–Lahti | Statement: [Finnish national road 4, hasMotorwaySection, Helsinki–Lahti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotorwaySection Context triple: [Finnish national road 4, hasMotorwaySection, Helsinki–Lahti]
-
A.
hasSmartMotorwaySection
Indicates that a road or route includes at least one section designated and operated as a smart motorway.
-
B.
hasExpresswaySection
chosen
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
C.
isMotorwayIn
Indicates that a motorway is located within or passes through a specified geographic area or administrative region.
-
D.
isOnOrbitalMotorway
Indicates that one entity (typically a route or segment) lies on or forms part of an orbital motorway that encircles a city or area.
-
E.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:13 p.m.