Triple
T13692013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Osaka–Okayama section |
E328288
|
entity |
| Predicate | gaugeMillimetres |
P87150
|
FINISHED |
| Object | 1435 mm |
—
|
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: 1435 mm | Statement: [Shin-Osaka–Okayama section, gaugeMillimetres, 1435 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeMillimetres Context triple: [Shin-Osaka–Okayama section, gaugeMillimetres, 1435 mm]
-
A.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
B.
heightMillimeters
Indicates the vertical size or elevation of an entity measured in millimeters.
-
C.
designedToMeasure
Indicates that one entity was intentionally created or configured for the purpose of quantifying, assessing, or evaluating another entity or its properties.
-
D.
standardGaugeWidth
chosen
Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
-
E.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8746458819095ec1ba3c01ef31b |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.