Triple
T32852145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 389 |
E840278
|
entity |
| Predicate | documentURL |
P158312
|
FINISHED |
| Object | https://undocs.org/S/RES/389(1976) |
—
|
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: https://undocs.org/S/RES/389(1976) | Statement: [UN Security Council Resolution 389, documentURL, https://undocs.org/S/RES/389(1976)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentURL Context triple: [UN Security Council Resolution 389, documentURL, https://undocs.org/S/RES/389(1976)]
-
A.
documentLocation
chosen
Indicates the physical or digital place where a document is stored, kept, or can be accessed.
-
B.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
-
C.
documentAtIssue
Indicates that a particular document is the specific item under consideration or dispute in a given context or proceeding.
-
D.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
E.
documentFeature
Indicates that a document possesses, exhibits, or is characterized by a particular feature or attribute.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:17 a.m.