Triple
T36107330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Rail |
E1044395
|
entity |
| Predicate | includesServicesOf |
P132992
|
FINISHED |
| Object | multiple train operating companies |
—
|
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: multiple train operating companies | Statement: [National Rail, includesServicesOf, multiple train operating companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesServicesOf Context triple: [National Rail, includesServicesOf, multiple train operating companies]
-
A.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
B.
includesServiceFrom
chosen
Indicates that one entity’s offering or package contains, incorporates, or makes use of a service provided by another entity.
-
C.
hasConstituentServicesIn
Indicates that an entity provides constituent services within a specified geographic or jurisdictional area.
-
D.
includesServicePattern
Indicates that one entity contains or incorporates a particular service pattern as part of its structure or configuration.
-
E.
hasServiceFrom
Indicates that one entity receives or benefits from a service provided by another entity.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.