Triple
T12787613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 2 of Manchester Airport |
E305671
|
entity |
| Predicate | parentRunwayDesignation |
P8866
|
FINISHED |
| Object | 05L/23R |
—
|
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: 05L/23R | Statement: [Runway 2 of Manchester Airport, parentRunwayDesignation, 05L/23R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentRunwayDesignation Context triple: [Runway 2 of Manchester Airport, parentRunwayDesignation, 05L/23R]
-
A.
hasRunwayDesignationSide
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
B.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
C.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
D.
hasRunwayNumber
chosen
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
E.
usesRunwayNumberingConvention
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5dbdb88190a1b06721ada51627 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.