Triple
T30048387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOTV |
E763523
|
entity |
| Predicate | hasRunwayOrientationPrefix |
P6272
|
FINISHED |
| Object | VO |
—
|
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: VO | Statement: [VOTV, hasRunwayOrientationPrefix, VO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayOrientationPrefix Context triple: [VOTV, hasRunwayOrientationPrefix, VO]
-
A.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
B.
hasRunwayConfiguration
Indicates a specific arrangement or setup of runways associated with an airport, airfield, or similar facility.
-
C.
hasRunwayDesignationSide
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
D.
hasRunwayDesignatorType
Indicates the specific type or classification of a runway’s designator used to identify that runway.
-
E.
hasRunwayPosition
Indicates the spatial or designated placement of an aircraft or object relative to a specific 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 6:54 p.m.