Triple
T4312800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alton railway station |
E94111
|
entity |
| Predicate | heritageTrackGauge |
P391
|
FINISHED |
| Object | standard 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: standard gauge | Statement: [Alton railway station, heritageTrackGauge, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageTrackGauge Context triple: [Alton railway station, heritageTrackGauge, standard gauge]
-
A.
trackGauge
chosen
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
historicalGauge
Indicates that one entity serves as a gauge, measure, or reference point for understanding the historical state, level, or condition of another entity.
-
C.
heritageFunction
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
D.
heritageId
Indicates that one entity serves as the heritage identifier or heritage reference code associated with another entity.
-
E.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d8bff88190bcf7dd419d5f4312 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:11 p.m.