Triple
T38188772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | hasCoachOperator |
P14541
|
FINISHED |
| Object | National Express |
E305024
|
NE 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: National Express | Statement: [London–Manchester, hasCoachOperator, National Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoachOperator Context triple: [London–Manchester, hasCoachOperator, National Express]
-
A.
hasCoachCharacter
Indicates that one entity serves as the coach or trainer character associated with another entity.
-
B.
isActiveAsCoach
Indicates that an entity is currently functioning in the role of a coach within a given context or organization.
-
C.
requiresCoach
Indicates that one entity depends on or must have the involvement, guidance, or supervision of a coach in order for an action, process, or state to occur or be valid.
-
D.
hasCoachOfCentre
Indicates that an entity serves as the coach associated with a particular centre.
-
E.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
- F. None of above.
Provenance (4 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b3fae14819083c6191c451d97fd |
completed | June 28, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.