Triple
T20039039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KGSP |
E497359
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object | Runway 4/22 |
—
|
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 4/22 | Statement: [KGSP, hasRunway, Runway 4/22]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 4/22 Context triple: [KGSP, hasRunway, Runway 4/22]
-
A.
Runway 4/22
Runway 4/22 is a primary paved runway at Southwest Georgia Regional Airport in Albany, Georgia, used for general aviation and commercial flight operations.
-
B.
Runway 4/22
chosen
Runway 4/22 is one of the primary paved runways at Fayetteville Regional Airport in North Carolina, used for takeoffs and landings aligned roughly northeast–southwest.
-
C.
Runway 4/22
Runway 4/22 is the primary paved runway at Culpeper Regional Airport in Virginia, used for general aviation takeoffs and landings.
-
D.
Runway 4/22
Runway 4/22 is one of the primary paved runways at Evansville Regional Airport in Indiana, used for handling a range of commercial and general aviation aircraft operations.
-
E.
Runway 4/22
Runway 4/22 is a primary paved runway at Cherokee County Regional Airport used for general aviation takeoffs and landings.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662e9e99c81909b7d50eac893c414 |
completed | April 20, 2026, 5:31 p.m. |
Created at: April 11, 2026, 3:36 p.m.