Triple
T16906451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Oregon Regional Airport |
E424575
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | PDT |
E1240091
|
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: PDT | Statement: [Eastern Oregon Regional Airport, FAAcode, PDT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PDT Context triple: [Eastern Oregon Regional Airport, FAAcode, PDT]
-
A.
PDT
chosen
PDT is the three-letter IATA airport code assigned to Eastern Oregon Regional Airport in Pendleton, Oregon, United States.
-
B.
PST
PST is the standard time observed in the Pacific Time Zone of North America, typically eight hours behind Coordinated Universal Time (UTC−8).
-
C.
PST
PST is the Norwegian Police Security Service, Norway’s domestic intelligence and security agency responsible for counterterrorism, counterintelligence, and protecting national security.
-
D.
PTP
PTP is a standardized protocol used to transfer digital images from cameras and other imaging devices to computers and other hosts.
-
E.
PTP
PTP is the IATA airport code for Pointe-à-Pitre International Airport, the main air gateway to Guadeloupe in the Caribbean.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca392ff48190ab28f0bd3e9fc376 |
completed | April 18, 2026, 6:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfcedb58819087c31200c01f40b7 |
completed | May 10, 2026, 6:34 p.m. |
Created at: April 10, 2026, 5:30 a.m.