Triple
T5824308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castleton railway station |
E129183
|
entity |
| Predicate | hasTimetablePosterBoards |
P5950
|
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: [Castleton railway station, hasTimetablePosterBoards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetablePosterBoards Context triple: [Castleton railway station, hasTimetablePosterBoards, yes]
-
A.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
hasServiceBoard
Indicates that an entity is associated with or connected to a specific service board, such as a panel or group responsible for providing or overseeing services.
-
C.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
D.
hasVillageBoard
Indicates that an entity is associated with or governed by a specific village board.
-
E.
hasLocalBoards
Indicates that an entity is associated with one or more governing or administrative boards operating at a local or regional level.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.