Triple
T16806144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFB Comox |
E408486
|
entity |
| Predicate | hasSecondaryRunwayOrientation |
P6272
|
FINISHED |
| Object | 18/36 |
—
|
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: 18/36 | Statement: [CFB Comox, hasSecondaryRunwayOrientation, 18/36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryRunwayOrientation Context triple: [CFB Comox, hasSecondaryRunwayOrientation, 18/36]
-
A.
hasOppositeRunway
Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
-
B.
hasParallelRunwayIndicator
Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
-
C.
hasParallelRunway
Indicates that one runway is parallel in orientation and alignment to another runway.
-
D.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cc25dc81909443b2c83155267a |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.