Triple
T16988111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardlui railway station |
E412121
|
entity |
| Predicate | requestStop |
P111700
|
FINISHED |
| Object | some services call 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: some services call on request | Statement: [Ardlui railway station, requestStop, some services call on request]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestStop Context triple: [Ardlui railway station, requestStop, some services call on request]
-
A.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
B.
hasRequestStops
chosen
Indicates that a transportation service includes one or more stops that are made only upon specific passenger request rather than by default.
-
C.
replyForStop
Indicates that one entity provides a reply or response specifically concerning a stop event or stopping action initiated by another entity.
-
D.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
E.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27cd2048190800a60ae653e11e1 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.