Triple
T37248487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumoi Main Line |
E923926
|
entity |
| Predicate | extensionCompleted |
P187673
|
FINISHED |
| Object | to Mashike in 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: to Mashike in 1921 | Statement: [Rumoi Main Line, extensionCompleted, to Mashike in 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionCompleted Context triple: [Rumoi Main Line, extensionCompleted, to Mashike in 1921]
-
A.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
B.
extensionTerminus
Indicates the endpoint or final limit to which something is extended or continues.
-
C.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
D.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
E.
extensionActivity
Indicates that one activity serves as an extension, follow-up, or supplementary continuation of another activity.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.