Triple
T34196676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barotseland independence activists |
E877260
|
entity |
| Predicate | frameCauseAs |
P694
|
FINISHED |
| Object | decolonization issue |
—
|
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: decolonization issue | Statement: [Barotseland independence activists, frameCauseAs, decolonization issue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameCauseAs Context triple: [Barotseland independence activists, frameCauseAs, decolonization issue]
-
A.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
fireCauseContext
Indicates the contextual circumstances or conditions that contributed to causing a fire.
-
D.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710296d748190badcd84374991840 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.