Triple
T38102591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Flight Information Region |
E951424
|
entity |
| Predicate | servesAirportCluster |
P202552
|
FINISHED |
| Object | Heathrow 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: Heathrow Airport | Statement: [London Flight Information Region, servesAirportCluster, Heathrow Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAirportCluster Context triple: [London Flight Information Region, servesAirportCluster, Heathrow Airport]
-
A.
servesAirport
Indicates that a transportation service or route provides access to and operates for a particular airport.
-
B.
servesAirportIATA
Indicates that a transportation service or facility operates routes to or from the airport identified by the given IATA code.
-
C.
servesAirportICAO
Indicates that a transportation service or facility operates routes to or from the airport identified by the given ICAO code.
-
D.
servesAirportType
Indicates that a transportation service or facility provides service to, or is designated for, a specific type or category of airport.
-
E.
servesAirportLine
Indicates that a transportation service or route operates on and provides service to a specific airport line.
- F. None of above. chosen
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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a008eba6de8819083165152448f6071 |
completed | May 10, 2026, 1:57 p.m. |
Created at: May 3, 2026, 4:21 p.m.