Triple
T24396064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berney Arms railway station |
E615029
|
entity |
| Predicate | requestStopProcedure |
P111700
|
FINISHED |
| Object | trains stop only on request |
—
|
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: trains stop only on request | Statement: [Berney Arms railway station, requestStopProcedure, trains stop only on request]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestStopProcedure Context triple: [Berney Arms railway station, requestStopProcedure, trains stop only on request]
-
A.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
B.
replyForStop
Indicates that one entity provides a reply or response specifically concerning a stop event or stopping action initiated by another entity.
-
C.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
-
D.
canStopService
Indicates that an entity has the authority or capability to terminate or halt a particular service.
-
E.
hasRequestStops
chosen
Indicates that a transportation service includes one or more stops that are made only upon specific passenger request rather than by default.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d69b5c81908cf6143374934f5c |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.