Triple
T33674088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 8/26 |
E862708
|
entity |
| Predicate | runwayNumber8MagneticHeading |
P70220
|
FINISHED |
| Object | approximately 080 degrees |
—
|
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: approximately 080 degrees | Statement: [Runway 8/26, runwayNumber8MagneticHeading, approximately 080 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayNumber8MagneticHeading Context triple: [Runway 8/26, runwayNumber8MagneticHeading, approximately 080 degrees]
-
A.
runwayEndHeading
chosen
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
B.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
C.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
D.
usesRunwayNumberingConvention
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
-
E.
runwayName
Indicates the designated name or identifier assigned to a runway.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:43 a.m.