Triple
T33674089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 8/26 |
E862708
|
entity |
| Predicate | runwayNumber26MagneticHeading |
P70220
|
FINISHED |
| Object | approximately 260 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 260 degrees | Statement: [Runway 8/26, runwayNumber26MagneticHeading, approximately 260 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayNumber26MagneticHeading Context triple: [Runway 8/26, runwayNumber26MagneticHeading, approximately 260 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.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
-
C.
runwayWidth
Indicates the measured width of a runway as a spatial dimension.
-
D.
runwayName
Indicates the designated name or identifier assigned to a runway.
-
E.
runway06_24Use
Indicates the use or operation of runway 06/24 for aircraft movements or related runway activities.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:43 a.m.