Triple
T33691267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemsley Down depot |
E863186
|
entity |
| Predicate | roleOnRailway |
P153871
|
FINISHED |
| Object | main maintenance facility |
—
|
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: main maintenance facility | Statement: [Kemsley Down depot, roleOnRailway, main maintenance facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnRailway Context triple: [Kemsley Down depot, roleOnRailway, main maintenance facility]
-
A.
roleInBulletTrain
Indicates the specific function, position, or responsibility an entity has within the context of a bullet train system or operation.
-
B.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
-
C.
undergroundRailroadRole
Indicates the specific role or function an entity played within the operations or support network of the Underground Railroad.
-
D.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
E.
railwayIndustryRole
chosen
Indicates a role, function, or position that an entity holds within the railway industry.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.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: May 1, 2026, 1:43 a.m.