Triple
T25327797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VECC |
E635064
|
entity |
| Predicate | associatedWithRunwayDirection |
P54806
|
FINISHED |
| Object | 01R/19L |
—
|
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: 01R/19L | Statement: [VECC, associatedWithRunwayDirection, 01R/19L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRunwayDirection Context triple: [VECC, associatedWithRunwayDirection, 01R/19L]
-
A.
associatedWithRunways
Indicates a relationship where something (such as an object, facility, or feature) is linked or connected to one or more runways.
-
B.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
C.
hasOppositeRunway
Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
-
D.
runwayAdjacentTo
Indicates that a runway is directly next to or alongside another feature or area, with no significant separation between them.
-
E.
hasRunwayDesignationSide
chosen
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 21, 2026, 1:30 p.m.