Triple
T38392668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HXX |
E899765
|
entity |
| Predicate | operatorOnRoutes |
P84215
|
FINISHED |
| Object | Heathrow Express |
E46241
|
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: Heathrow Express | Statement: [HXX, operatorOnRoutes, Heathrow Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOnRoutes Context triple: [HXX, operatorOnRoutes, Heathrow Express]
-
A.
routeOperator
chosen
Indicates that an agent operates, manages, or is responsible for running a particular route or service path.
-
B.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
C.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
D.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
E.
exportRoute
Indicates the route or pathway through which goods, services, or data are exported from one location or entity to another.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c27fb6c08190966d39bc68dfe3d7 |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:31 p.m.