Triple
T10335811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KEYW |
E242998
|
entity |
| Predicate | hasShortRunway |
P20697
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KEYW, hasShortRunway, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortRunway Context triple: [KEYW, hasShortRunway, yes]
-
A.
runwaySupportsAircraftType
Indicates that a particular runway is suitable and certified for use by a specified type of aircraft.
-
B.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
C.
hasRunwayLengthCategory
chosen
Indicates that an airport or airfield is associated with a specific categorical range of runway lengths (e.g., short, medium, long).
-
D.
hasRunwayAccessVia
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
-
E.
hasRunwayAccessTo
Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:53 a.m.