Triple
T31901370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxenhope railway station |
E814430
|
entity |
| Predicate | hasBuffet |
P46099
|
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, hasBuffet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuffet Context triple: [Oxenhope railway station, hasBuffet, true]
-
A.
offersBuffet
chosen
Indicates that one entity provides a buffet-style service or meal option to another entity.
-
B.
hasDiningComponent
Indicates that something includes or is associated with a dining-related part, feature, or function.
-
C.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
D.
hasBanquetCapacity
Indicates that an entity can accommodate a specified number of people when arranged in a banquet-style setup.
-
E.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
- 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_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 30, 2026, 11:59 p.m.