Triple
T36261471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific/Bougainville |
E892097
|
entity |
| Predicate | ianaRegionCode |
P4816
|
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: [Pacific/Bougainville, ianaRegionCode, PG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaRegionCode Context triple: [Pacific/Bougainville, ianaRegionCode, PG]
-
A.
iccRegion
Indicates that one entity is associated with, located in, or falls under the jurisdiction of a particular ICC (International Criminal Court) region.
-
B.
ISTATCode
Indicates that an entity is associated with a specific ISTAT (Italian National Institute of Statistics) classification or code.
-
C.
ianaArea
chosen
Indicates that one entity is associated with, or falls within, a specific IANA-defined geographic or administrative area represented by the other entity.
-
D.
ITURegion
Indicates the International Telecommunication Union (ITU) regional classification to which an entity (such as a location or station) belongs.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
- F. None of above.
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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b6227808819085a3d728329481a0 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.