Triple
T1955997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson Valley Regional Airport |
E42268
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | POU |
E218470
|
NE 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: POU | Statement: [Hudson Valley Regional Airport, FAA LID, POU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: POU Context triple: [Hudson Valley Regional Airport, FAA LID, POU]
-
A.
POU
chosen
POU is the IATA airport code for Hudson Valley Regional Airport, a public airport serving the Poughkeepsie area in New York’s Hudson Valley.
-
B.
KPOU
KPOU is the ICAO airport code for Hudson Valley Regional Airport in Dutchess County, New York.
-
C.
Po
The Po is Italy’s longest and most important river, flowing eastward across northern Italy from the Alps to the Adriatic Sea.
-
D.
POC
POC is the commonly used abbreviation for the Postal Operations Council, the executive body responsible for overseeing the operational, commercial, and technical activities of the Universal Postal Union.
-
E.
POL
POL is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Poland in international standards and data systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb37b4a38819099f98be92be91ade |
completed | March 7, 2026, 5:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae031cc7948190a4d9593cd118c149 |
completed | March 8, 2026, 11:15 p.m. |
Created at: March 4, 2026, 7:36 p.m.