Triple
T13588486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indonesian railway network |
E324631
|
entity |
| Predicate | dominantTrackGauge |
P74353
|
FINISHED |
| Object | 1067 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: 1067 mm | Statement: [Indonesian railway network, dominantTrackGauge, 1067 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantTrackGauge Context triple: [Indonesian railway network, dominantTrackGauge, 1067 mm]
-
A.
dominantGauge
chosen
Indicates that one gauge in a system serves as the primary or controlling reference against which other gauges or measurements are compared or regulated.
-
B.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
C.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
D.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
E.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb055cc98819091fab597b69e5e3e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.