Triple
T37248488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumoi Main Line |
E923926
|
entity |
| Predicate | formerSection |
P116490
|
FINISHED |
| Object | Rumoi – Mashike section |
—
|
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: Rumoi – Mashike section | Statement: [Rumoi Main Line, formerSection, Rumoi – Mashike section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSection Context triple: [Rumoi Main Line, formerSection, Rumoi – Mashike section]
-
A.
formerPart
chosen
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
B.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
C.
former
Indicates that an entity previously held a role, status, or relationship but no longer does so in the present.
-
D.
formerRackSection
Indicates that an entity was previously part of a specified rack section but is no longer associated with it.
-
E.
formerField
Indicates that an entity previously had a particular field, role, or area of activity, but no longer does.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:15 p.m.