Triple
T19250165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amur–Yakutsk Mainline |
E481366
|
entity |
| Predicate | majorConstructionResumption |
P5779
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Amur–Yakutsk Mainline, majorConstructionResumption, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorConstructionResumption Context triple: [Amur–Yakutsk Mainline, majorConstructionResumption, 1970s]
-
A.
constructionResumed
chosen
Indicates that previously halted construction activity on an entity or project has started again.
-
B.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
C.
majorConstructionUnder
Indicates that a location or structure is currently undergoing significant construction work or large-scale building activity.
-
D.
constructionResumedBy
Indicates that a previously halted or paused construction activity is restarted or continued by a specified agent or entity.
-
E.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3001308190913e24343769be8d |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.