Triple
T1466406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bougainville Island |
E27031
|
entity |
| Predicate | conflictPeriod |
P28865
|
FINISHED |
| Object | late 1980s to late 1990s |
—
|
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: late 1980s to late 1990s | Statement: [Bougainville Island, conflictPeriod, late 1980s to late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictPeriod Context triple: [Bougainville Island, conflictPeriod, late 1980s to late 1990s]
-
A.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
religiousConflictPeriod
Indicates a period of time during which conflicts or hostilities occur that are primarily motivated or structured by religious differences or tensions.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5bb4e288190997c7e8985e9a2bd |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:01 p.m.