Triple
T11059085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusaka Protocol |
E261456
|
entity |
| Predicate | phaseOfProcess |
P4106
|
FINISHED |
| Object | Angolan peace process of the 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: Angolan peace process of the 1990s | Statement: [Lusaka Protocol, phaseOfProcess, Angolan peace process of the 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseOfProcess Context triple: [Lusaka Protocol, phaseOfProcess, Angolan peace process of the 1990s]
-
A.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
B.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
C.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
D.
phaseType
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
-
E.
phaseInStructure
Indicates that an entity occurs as a particular phase or stage within the structural organization or composition of 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a4f3f88190a29710f64cef9d25 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.