Triple
T25989697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minobu Line |
E646310
|
entity |
| Predicate | trackGaugeUnit |
P159641
|
FINISHED |
| Object | millimetre |
—
|
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: millimetre | Statement: [Minobu Line, trackGaugeUnit, millimetre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeUnit Context triple: [Minobu Line, trackGaugeUnit, millimetre]
-
A.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
trackGaugeOptions
Indicates the available or applicable gauge (measurement) configurations that can be used for a given track.
-
C.
formerTrackGauge
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
D.
gaugeConversion
Indicates a relationship where one measurement or scale is converted into another corresponding measurement or scale.
-
E.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605469f7881909fb9d981d79def18 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:55 a.m.