Triple
T31901366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxenhope railway station |
E814430
|
entity |
| Predicate | hasEngineShed |
P188799
|
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, hasEngineShed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineShed Context triple: [Oxenhope railway station, hasEngineShed, true]
-
A.
hasCarriageShed
Indicates that an entity possesses or includes a shed or structure specifically used for storing or housing carriages.
-
B.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
C.
usesEngineCycle
Indicates that one entity operates or functions by employing the engine cycle specified by another entity.
-
D.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
E.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 30, 2026, 11:59 p.m.