Triple
T17153561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport News/Williamsburg International Airport |
E416281
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | PHF |
E1252855
|
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: PHF | Statement: [Newport News/Williamsburg International Airport, hasAbbreviation, PHF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PHF Context triple: [Newport News/Williamsburg International Airport, hasAbbreviation, PHF]
-
A.
PHF
chosen
PHF is the three-letter FAA airport code for Newport News/Williamsburg International Airport in Virginia, United States.
-
B.
HPH
HPH is the IATA airport code for Cat Bi International Airport serving Hai Phong, Vietnam.
-
C.
FHP
FHP is the state law enforcement agency responsible for highway safety and traffic enforcement across Florida’s roadways.
-
D.
PH
PH is the vehicle registration code used on license plates for vehicles registered in Ploiești, Romania.
-
E.
PH
PH is a postcode area in the United Kingdom covering Perth and surrounding parts of central and northern Scotland.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4092c40819096359ff90af16c3e |
completed | April 18, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0148337a348190b8739eb3f553f1d9 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:37 a.m.