Triple
T17441578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okehampton railway station |
E424666
|
entity |
| Predicate | hasHeritageServices |
P64608
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Okehampton railway station, hasHeritageServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageServices Context triple: [Okehampton railway station, hasHeritageServices, yes]
-
A.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
hasHeritageOrganization
Indicates that an entity is associated with, or belongs to, a particular heritage-related organization.
-
C.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
D.
heritageService
chosen
Indicates that an entity provides, manages, or is associated with services related to the preservation, interpretation, or promotion of cultural or natural heritage.
-
E.
hasHeritageContext
Indicates that something is associated with, influenced by, or situated within a particular cultural, historical, or heritage-related context.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff75538819083f77756d39a1aaa |
completed | April 19, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.