Triple
T25980748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Bougainville independence referendum |
E646062
|
entity |
| Predicate | majorityChoice |
P4520
|
FINISHED |
| Object | independence |
—
|
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: independence | Statement: [2019 Bougainville independence referendum, majorityChoice, independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorityChoice Context triple: [2019 Bougainville independence referendum, majorityChoice, independence]
-
A.
majorityVote
chosen
Indicates that a decision or outcome is determined by the option receiving more than half of the votes among a group.
-
B.
majorityType
Indicates that one type or category constitutes more than half of the instances within a given set or context.
-
C.
votedWithMajorityIn
Indicates that an entity cast its vote in alignment with the majority decision within a given voting event or body.
-
D.
majorityOrientation
Indicates that one orientation or direction is held by more than half of the relevant entities in a given context.
-
E.
majorityOpinion
Indicates that a particular opinion is held by more than half of the relevant group or decision-making body.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 8:54 a.m.