Triple
T37248484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumoi Main Line |
E923926
|
entity |
| Predicate | lineLengthBeforeClosures |
P39661
|
FINISHED |
| Object | approximately 66.8 km |
—
|
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: approximately 66.8 km | Statement: [Rumoi Main Line, lineLengthBeforeClosures, approximately 66.8 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineLengthBeforeClosures Context triple: [Rumoi Main Line, lineLengthBeforeClosures, approximately 66.8 km]
-
A.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
B.
mostLinesClosed
Indicates that the majority of the lines or routes associated with an entity are currently closed or non-operational.
-
C.
lineClosedUnder
Indicates that a given line is closed under a specified operation, meaning applying the operation to any elements on the line produces a result that also lies on the same line.
-
D.
hasLineLength
chosen
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
E.
usesLineFolding
Indicates that an entity applies line folding, breaking long lines into shorter ones according to specific rules or constraints.
- 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_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.