Triple
T17441588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okehampton railway station |
E424666
|
entity |
| Predicate | hasAccessibleAccess |
P127464
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Okehampton railway station, hasAccessibleAccess, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessibleAccess Context triple: [Okehampton railway station, hasAccessibleAccess, partial]
-
A.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
B.
hasAccessibleConnection
Indicates that there exists a way for one entity to reach or interact with another in a manner that meets defined accessibility requirements.
-
C.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
- 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_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. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.