Triple
T2281493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Coast railway line |
E51288
|
entity |
| Predicate | completedAsThroughRoute |
P36240
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [North Coast railway line, completedAsThroughRoute, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedAsThroughRoute Context triple: [North Coast railway line, completedAsThroughRoute, 1930]
-
A.
completedAsContinuousRoute
Indicates that an activity or journey was carried out in one uninterrupted, continuous sequence without breaks or segmentation.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
D.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
E.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21c405881908c4df7bee36136fe |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4368a88190956bc9ee89c0fd1f |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.