Triple
T8754549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strigino International Airport |
E208041
|
entity |
| Predicate | hasRunwayUsage |
P19339
|
FINISHED |
| Object | commercial aviation |
—
|
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: commercial aviation | Statement: [Strigino International Airport, hasRunwayUsage, commercial aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayUsage Context triple: [Strigino International Airport, hasRunwayUsage, commercial aviation]
-
A.
hasRunwayUse
chosen
Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
-
B.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
-
C.
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.
-
D.
hasRunwayOperations
Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
-
E.
hasRunwayAccessVia
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd83088819082cf54adc0c04243 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.