Triple
T35437637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papua New Guinea |
E1024252
|
entity |
| Predicate | countryCodeISO3166-1 alpha-2 |
P203668
|
FINISHED |
| Object | PG |
E1024252
|
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: PG | Statement: [Papua New Guinea, countryCodeISO3166-1 alpha-2, PG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeISO3166-1 alpha-2 Context triple: [Papua New Guinea, countryCodeISO3166-1 alpha-2, PG]
-
A.
countryCode2
chosen
Indicates that an entity is associated with a specific two-letter country code (ISO 3166-1 alpha-2).
-
B.
countryCode3
Indicates that an entity is associated with a specific three-letter (ISO 3166-1 alpha-3) country code.
-
C.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
D.
ISO3166-1Code
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
-
E.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
- F. None of above.
Provenance (4 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384029b4cc819083a6a873f8512ec7 |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: May 3, 2026, 4:04 p.m.