Triple
T20707632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dovrebanen |
E508945
|
entity |
| Predicate | completedAsThroughRouteYear |
P141171
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Dovrebanen, completedAsThroughRouteYear, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedAsThroughRouteYear Context triple: [Dovrebanen, completedAsThroughRouteYear, 1921]
-
A.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
B.
workCompletionYear
Indicates the calendar year in which a particular work, project, or task was completed.
-
C.
typicallyCompletedInYearLevel
Indicates the usual school year level in which an activity, course, or requirement is completed.
-
D.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
E.
completedAsContinuousRoute
Indicates that an activity or journey was carried out in one uninterrupted, continuous sequence without breaks or segmentation.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1952e888190877b79933970f7b0 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:14 p.m.