Triple
T30947831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 07/25 |
E788445
|
entity |
| Predicate | runwayEnd25Direction |
P70220
|
FINISHED |
| Object | west-southwest |
—
|
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: west-southwest | Statement: [Runway 07/25, runwayEnd25Direction, west-southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayEnd25Direction Context triple: [Runway 07/25, runwayEnd25Direction, west-southwest]
-
A.
runwayEndHeading
chosen
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
B.
hasRightRunwayIn25Direction
Indicates that an entity (typically an airport or airfield) possesses a right-hand runway aligned or oriented in the 25 direction.
-
C.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
-
D.
runwayAdjacentTo
Indicates that a runway is directly next to or alongside another feature or area, with no significant separation between them.
-
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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 8:53 p.m.