Triple
T26810254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otford railway station |
E671969
|
entity |
| Predicate | hasStationFacility |
P1711
|
FINISHED |
| Object | ticket office |
—
|
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: ticket office | Statement: [Otford railway station, hasStationFacility, ticket office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationFacility Context triple: [Otford railway station, hasStationFacility, ticket office]
-
A.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
C.
hasStationBuilding
chosen
Indicates that a station is associated with or includes a station building as part of its facilities.
-
D.
hasUpperStationFacility
Indicates that an entity possesses or is associated with a facility located at an upper station (e.g., the upper end of a transport or transit system).
-
E.
hasStationStructure
Indicates that an entity possesses or is associated with a particular station-related physical structure.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 4:28 a.m.