Triple
T14046976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS |
E337980
|
entity |
| Predicate | gaugeTypeServed |
P39342
|
FINISHED |
| Object | 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: broad gauge | Statement: [MAS, gaugeTypeServed, broad gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeTypeServed Context triple: [MAS, gaugeTypeServed, broad gauge]
-
A.
gaugeType
chosen
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
B.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
C.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
D.
dominantGauge
Indicates that one gauge in a system serves as the primary or controlling reference against which other gauges or measurements are compared or regulated.
-
E.
standardGaugeWidth
Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.