Triple
T17607541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea–Cardiff line |
E428872
|
entity |
| Predicate | hasExpressServices |
P16277
|
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, hasExpressServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressServices Context triple: [Swansea–Cardiff line, hasExpressServices, yes]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
hasExpressSegments
chosen
Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
-
C.
primaryExpressService
Indicates that an entity provides or is associated with the main, prioritized express-level service in a given context.
-
D.
canExpress
Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
-
E.
hasCenterExpressTracks
Indicates that the subject location or facility contains express railway tracks running through its central area or core.
- 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.