Triple
T38188779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | hasAirportInManchester |
P37080
|
FINISHED |
| Object | Manchester Airport |
—
|
NE NERFINISHED |
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: Manchester Airport | Statement: [London–Manchester, hasAirportInManchester, Manchester Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirportInManchester Context triple: [London–Manchester, hasAirportInManchester, Manchester Airport]
-
A.
majorAirportInLondon
Indicates that an airport is a primary or significant airport located within London.
-
B.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
-
C.
hasAirportInVicinity
Indicates that an entity is located near or served by an airport in its surrounding area.
-
D.
hasEndpointAirport
chosen
Indicates that something, such as a route or flight, has a specific airport as one of its terminal endpoints.
-
E.
hasAirportCenter
Indicates that an airport is centrally located within, or serves as the main air transport hub for, a specified area or region.
- 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_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:29 p.m.