Triple
T29901372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Depositary Notifications (CN series) |
E759415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official UN document series |
C15414
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: official UN document series Context triple: [Depositary Notifications (CN series), instanceOf, official UN document series]
-
A.
United Nations document series
chosen
A United Nations document series is a categorized collection of official UN documents grouped under a common symbol or theme to organize and track related records over time.
-
B.
United Nations outcome document
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
-
C.
United Nations report
A United Nations report is an official document produced by UN bodies that presents analysis, findings, and recommendations on international issues such as peace, development, human rights, and the environment.
-
D.
United Nations protocol
United Nations protocol is the formal set of rules, procedures, and diplomatic customs that govern conduct, precedence, ceremonies, and official interactions within and around the United Nations.
-
E.
United Nations information system
A United Nations information system is an integrated framework of technologies, databases, and processes used across UN entities to collect, manage, analyze, and disseminate data and knowledge in support of the organization’s mandates and decision-making.
- F. None of above.
Provenance (1 batch)
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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:06 p.m.