Triple
T38188783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | isMajorLeisureTravelCorridor |
P101130
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [London–Manchester, isMajorLeisureTravelCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLeisureTravelCorridor Context triple: [London–Manchester, isMajorLeisureTravelCorridor, true]
-
A.
isMajorTourismRoute
chosen
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
B.
isMajorPassengerRoute
Indicates that a transportation route serves as a primary corridor carrying a high volume of passenger traffic between locations.
-
C.
isMajorTransportAxisIn
Indicates that a route or corridor functions as a primary or heavily used transportation pathway within a specified area or region.
-
D.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
E.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 3, 2026, 4:29 p.m.