Triple
T26283586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Solomons Province |
E661069
|
entity |
| Predicate | statusChangedTo |
P35872
|
FINISHED |
| Object | Autonomous Region of Bougainville |
—
|
NE NERFINISHED |
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: Autonomous Region of Bougainville | Statement: [North Solomons Province, statusChangedTo, Autonomous Region of Bougainville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusChangedTo Context triple: [North Solomons Province, statusChangedTo, Autonomous Region of Bougainville]
-
A.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
statusChangeRule
Indicates a rule or condition that governs how and when an entity’s status is allowed to change from one state to another.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
-
E.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 10:02 p.m.