Triple
T10400263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaenau Ffestiniog Station |
E245126
|
entity |
| Predicate | gaugeServed |
P93711
|
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: [Blaenau Ffestiniog Station, gaugeServed, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeServed Context triple: [Blaenau Ffestiniog Station, gaugeServed, standard gauge]
-
A.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
B.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
C.
isServedOn
Indicates that one item (typically food or drink) is presented or provided atop or together with a particular surface, container, or accompaniment.
-
D.
servedTimeAt
Indicates the specific time period during which an entity was served or received service at a particular place or context.
-
E.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d2e8488190b2bb8f8509903804 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:07 p.m.