Triple
T26476469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 18 |
E666049
|
entity |
| Predicate | belongsToRunwayPair |
P66860
|
FINISHED |
| Object | Runway 18/36 |
—
|
NE NERFINISHED |
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: Runway 18/36 | Statement: [Runway 18, belongsToRunwayPair, Runway 18/36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRunwayPair Context triple: [Runway 18, belongsToRunwayPair, Runway 18/36]
-
A.
associatedWithRunways
Indicates a relationship where something (such as an object, facility, or feature) is linked or connected to one or more runways.
-
B.
runwayPair
Indicates that two runways are associated or grouped together as a functional pair, typically for coordinated or complementary use.
-
C.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
D.
hasOppositeRunway
chosen
Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
-
E.
hasRunwaySide
Indicates that a runway is located on or associated with a particular side or boundary of another feature (such as an airport or airfield area).
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 12:23 a.m.