Triple
T8185657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamagata Shinkansen |
E191174
|
entity |
| Predicate | gaugeBeforeConversion |
P9777
|
FINISHED |
| Object | 1,067 mm narrow gauge |
—
|
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: 1,067 mm narrow gauge | Statement: [Yamagata Shinkansen, gaugeBeforeConversion, 1,067 mm narrow gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeBeforeConversion Context triple: [Yamagata Shinkansen, gaugeBeforeConversion, 1,067 mm narrow gauge]
-
A.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
B.
upgradedToBroadGauge
Indicates that something previously using a narrower or different railway track gauge has been converted to use broad gauge.
-
C.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
D.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
E.
wasPreviouslyMeasuredAs
chosen
Indicates that an entity had a specific measurement or value at an earlier time, which may differ from its current measurement.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c52407c8190bd366fce6d4e02cd |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.