Triple
T36261540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papua New Guinea Time |
E892099
|
entity |
| Predicate | regionCodeISO3166 |
P201661
|
FINISHED |
| Object | PG |
—
|
LITERAL 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 Time, regionCodeISO3166, PG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCodeISO3166 Context triple: [Papua New Guinea Time, regionCodeISO3166, PG]
-
A.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
B.
regionCodeUsedIn
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
C.
ISO3166-2RegionCode
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
-
D.
usesISO3166-2Code
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
E.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
- F. None of above. chosen
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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
| PDg | Predicate description generation | batch_6a0010e304a08190a4d0a4fa11a9a3b3 |
completed | May 10, 2026, 5 a.m. |
Created at: May 3, 2026, 4:09 p.m.