Triple
T25414073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KCOS |
E636780
|
entity |
| Predicate | associatedRunwayUse |
P105006
|
FINISHED |
| Object | civil 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: civil aviation | Statement: [KCOS, associatedRunwayUse, civil aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRunwayUse Context triple: [KCOS, associatedRunwayUse, civil aviation]
-
A.
runwayUsage
Indicates that a particular runway is being used or assigned for aircraft operations such as takeoffs or landings.
-
B.
hasRunwayUse
Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
-
C.
runwayUsedAs
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
-
D.
associatedWithRunways
chosen
Indicates a relationship where something (such as an object, facility, or feature) is linked or connected to one or more runways.
-
E.
runwaysUsableAt
Indicates that certain runways at a location are available and suitable for use (e.g., for takeoff or landing) at a given time or under specified conditions.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 21, 2026, 1:55 p.m.