Triple
T13144305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papua New Guinean kina |
E312295
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | PGK |
E312293
|
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: PGK | Statement: [Papua New Guinean kina, ISO4217Code, PGK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PGK Context triple: [Papua New Guinean kina, ISO4217Code, PGK]
-
A.
PGK
chosen
PGK is the three-letter international currency code for the Papua New Guinean kina, the official currency of Papua New Guinea.
-
B.
PKC
PKC is a leading international cryptography conference focused on public-key cryptography research and advancements.
-
C.
PKC
PKC is the IATA airport code for Petropavlovsk-Kamchatsky Airport, a major air gateway to Russia’s Kamchatka Peninsula.
-
D.
PGC
PGC is an astronomical catalog that systematically lists and provides data on galaxies, including objects like the Leo II Dwarf Galaxy.
-
E.
PKB
PKB is the IATA airport code for Mid-Ohio Valley Regional Airport serving the Parkersburg–Vienna area in West Virginia, USA.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98bce3678819082a7aa1d83f20592 |
completed | April 10, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff09a964819097fbb37a7f11eac5 |
completed | May 3, 2026, 7:53 a.m. |
Created at: April 9, 2026, 9:10 p.m.