Triple
T19777389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barkley Regional Airport |
E475037
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | PAH |
—
|
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: PAH | Statement: [Barkley Regional Airport, FAA LID, PAH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PAH Context triple: [Barkley Regional Airport, FAA LID, PAH]
-
A.
PAH
chosen
PAH is the three-letter IATA airport code for Barkley Regional Airport in Paducah, Kentucky, United States.
-
B.
PAF
PAF is the acronym for the Pakistan Air Force, the aerial warfare branch of Pakistan’s armed forces.
-
C.
PAF
PAF is a Palestinian political organization known as the Palestinian Arab Front, active in Palestinian national and leftist politics.
-
D.
PAF
PAF is the vehicle registration code used on license plates for vehicles registered in the district of Pfaffenhofen an der Ilm in Bavaria, Germany.
-
E.
PAF
PAF is the acronym for the Philippine Air Force, the aerial warfare branch of the Armed Forces of the Philippines.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65361a8e08190b52944aab25e45fa |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:48 p.m.