Triple
T17607540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea–Cardiff line |
E428872
|
entity |
| Predicate | hasStoppingServices |
P17789
|
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: [Swansea–Cardiff line, hasStoppingServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoppingServices Context triple: [Swansea–Cardiff line, hasStoppingServices, yes]
-
A.
canStopService
Indicates that an entity has the authority or capability to terminate or halt a particular service.
-
B.
hasStop
chosen
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
C.
hasStopFeature
Indicates that one entity possesses or is equipped with a feature that enables stopping or halting an associated process, action, or movement.
-
D.
hasTerminalService
Indicates that one entity provides or is associated with a terminal-related service (such as an endpoint, station, or final service point) for another entity.
-
E.
hasStopType
Indicates that a stop or stopping point is classified as having a particular type or category of stop.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4ccef08190aeaa88670364bd74 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.