Triple
T3613759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Treaty Series, volume 78 |
E76549
|
entity |
| Predicate | containsDocumentType |
P13313
|
FINISHED |
| Object | full treaty texts |
—
|
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: full treaty texts | Statement: [United Nations Treaty Series, volume 78, containsDocumentType, full treaty texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDocumentType Context triple: [United Nations Treaty Series, volume 78, containsDocumentType, full treaty texts]
-
A.
documentTypeIncluded
chosen
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
B.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
C.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
-
D.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
E.
hasCorpusType
Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.