Triple
T26524497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinhagak Airport |
E670648
|
entity |
| Predicate | runway 12/30 orientation |
P6272
|
FINISHED |
| Object | 120/300 degrees magnetic |
—
|
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: 120/300 degrees magnetic | Statement: [Quinhagak Airport, runway 12/30 orientation, 120/300 degrees magnetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway 12/30 orientation Context triple: [Quinhagak Airport, runway 12/30 orientation, 120/300 degrees magnetic]
-
A.
runway12_30Usage
Indicates the use or operational status of runway 12/30 for aircraft movements or related airport activities.
-
B.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
E.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:30 a.m.