Triple
T6285842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberian gauge |
E140896
|
entity |
| Predicate | standardGaugeWidthComparison |
P69893
|
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: [Iberian gauge, standardGaugeWidthComparison, 1435 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardGaugeWidthComparison Context triple: [Iberian gauge, standardGaugeWidthComparison, 1435 mm]
-
A.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
B.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
C.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
D.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
E.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063fe59fc81908dbd968017771190 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.