Triple
T2876807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Army Airfield |
E56896
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | POB |
E306413
|
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: POB | Statement: [Pope Army Airfield, FAAcode, POB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: POB Context triple: [Pope Army Airfield, FAAcode, POB]
-
A.
POB
chosen
POB is the IATA airport code for Pope Army Airfield, a U.S. military airfield located adjacent to Fort Liberty in North Carolina.
-
B.
Po
The Po is Italy’s longest and most important river, flowing eastward across northern Italy from the Alps to the Adriatic Sea.
-
C.
POU
POU is the IATA airport code for Hudson Valley Regional Airport, a public airport serving the Poughkeepsie area in New York’s Hudson Valley.
-
D.
PO
PO is a UK postcode area covering Portsmouth and surrounding parts of Hampshire and West Sussex.
-
E.
PB
PB is the post-nominal abbreviation used to denote recipients of the Padma Bhushan, one of India’s highest civilian honors.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0061d048190bb1e5a01e7ceb0e2 |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b03153b5048190925bfacc07f2db66 |
completed | March 10, 2026, 2:57 p.m. |
Created at: March 6, 2026, 10:03 p.m.