Triple
T35629320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzbekistan Railways |
E1029541
|
entity |
| Predicate | standardGaugeUsed |
P87150
|
FINISHED |
| Object | 1520 mm broad 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: 1520 mm broad gauge | Statement: [Uzbekistan Railways, standardGaugeUsed, 1520 mm broad gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardGaugeUsed Context triple: [Uzbekistan Railways, standardGaugeUsed, 1520 mm broad gauge]
-
A.
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.
-
B.
standardGaugeWidthComparison
Indicates a comparison between the track gauge width of a railway and the standard gauge width to determine if it is equal to, narrower than, or wider than the standard.
-
C.
nonStandardGauge
Indicates that the gauge used in a railway or track segment deviates from the standard track gauge dimension.
-
D.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
E.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.