Triple
T27450452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 23 |
E692423
|
entity |
| Predicate | hasRunwayPair |
P66861
|
FINISHED |
| Object | Runway 05/23 |
—
|
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: Runway 05/23 | Statement: [Runway 23, hasRunwayPair, Runway 05/23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayPair Context triple: [Runway 23, hasRunwayPair, Runway 05/23]
-
A.
hasRunwaySide
Indicates that a runway is located on or associated with a particular side or boundary of another feature (such as an airport or airfield area).
-
B.
hasRunwayCount
Indicates the number of runways that a given entity (such as an airport) possesses.
-
C.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
D.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
-
E.
runwayPair
chosen
Indicates that two runways are associated or grouped together as a functional pair, typically for coordinated or complementary use.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 12:47 p.m.