Triple
T34865395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arusha Peace and Reconciliation Agreement for Burundi |
E1004993
|
entity |
| Predicate | UNDocumentReference |
P181940
|
FINISHED |
| Object | S/2000/914 |
—
|
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: S/2000/914 | Statement: [Arusha Peace and Reconciliation Agreement for Burundi, UNDocumentReference, S/2000/914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNDocumentReference Context triple: [Arusha Peace and Reconciliation Agreement for Burundi, UNDocumentReference, S/2000/914]
-
A.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
B.
coreDocumentOf
Indicates that one entity serves as the primary or central document associated with, or defining, another entity.
-
C.
referentRecord
Indicates that one record serves as a reference or pointer to another record within a data or information structure.
-
D.
inUniverseReference
Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
-
E.
belongsToDocument
Indicates that something is a part of, associated with, or contained within a specific document.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.