Triple
T9664948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Rail Wales area |
E233678
|
entity |
| Predicate | includesServices |
P64716
|
FINISHED |
| Object | intercity rail services |
—
|
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: intercity rail services | Statement: [National Rail Wales area, includesServices, intercity rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesServices Context triple: [National Rail Wales area, includesServices, intercity rail services]
-
A.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
B.
hasConstituentServicesIn
chosen
Indicates that an entity provides constituent services within a specified geographic or jurisdictional area.
-
C.
includesServicePattern
Indicates that one entity contains or incorporates a particular service pattern as part of its structure or configuration.
-
D.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of another entity.
-
E.
serviceComponentsInclude
Indicates that a service is composed of, or functionally includes, specific component elements.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0e1ef481909c50a4ba5fd94583 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.