Triple
T36595736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luena Memorandum of Understanding |
E902792
|
entity |
| Predicate | implementedProcess |
P924
|
FINISHED |
| Object | disarmament of UNITA forces |
—
|
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: disarmament of UNITA forces | Statement: [Luena Memorandum of Understanding, implementedProcess, disarmament of UNITA forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedProcess Context triple: [Luena Memorandum of Understanding, implementedProcess, disarmament of UNITA forces]
-
A.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
B.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
D.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
E.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.