Triple
T31901383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxenhope railway station |
E814430
|
entity |
| Predicate | hasLocoStabling |
P18851
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oxenhope railway station, hasLocoStabling, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocoStabling Context triple: [Oxenhope railway station, hasLocoStabling, true]
-
A.
hasStabling
Indicates that one entity provides or contains stabling facilities (such as stalls or accommodation) for another, typically for animals like horses.
-
B.
hasStablingCapacity
Indicates the maximum number of animals or vehicles that a facility can accommodate for stabling or storage.
-
C.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
D.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
E.
hasRailYard
chosen
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 30, 2026, 11:59 p.m.