Triple
T35659194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Devon Railway |
E1030380
|
entity |
| Predicate | usedGaugeSystem |
P139806
|
FINISHED |
| Object | Brunel broad gauge |
—
|
NE NERFINISHED |
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: Brunel broad gauge | Statement: [South Devon Railway, usedGaugeSystem, Brunel broad gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedGaugeSystem Context triple: [South Devon Railway, usedGaugeSystem, Brunel broad gauge]
-
A.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
B.
previouslyHadGauge
chosen
Indicates that an entity had a particular gauge or measurement instrument at some time in the past, but does not necessarily have it now.
-
C.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
D.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
-
E.
gaugeConversion
Indicates a relationship where one measurement or scale is converted into another corresponding measurement or scale.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7997fc819099df7ddb772f9307 |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.