Triple
T21395500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 03/21 |
E527768
|
entity |
| Predicate | runwayEnd03TrueHeadingApprox |
P70220
|
FINISHED |
| Object | 030 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: 030 degrees | Statement: [Runway 03/21, runwayEnd03TrueHeadingApprox, 030 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayEnd03TrueHeadingApprox Context triple: [Runway 03/21, runwayEnd03TrueHeadingApprox, 030 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.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
-
C.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
D.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
E.
runwayAdjacentTo
Indicates that a runway is directly next to or alongside another feature or area, with no significant separation between them.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62ce3c5c81909e1e584e2f6667c8 |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:13 p.m.