Triple
T4420972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly Resolution 46/182 |
E95094
|
entity |
| Predicate | adoptedByConsensus |
P55879
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United Nations General Assembly Resolution 46/182, adoptedByConsensus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedByConsensus Context triple: [United Nations General Assembly Resolution 46/182, adoptedByConsensus, true]
-
A.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
adoptedByLeadersOf
Indicates that something has been formally accepted, endorsed, or implemented by the leaders of a specified group, organization, or community.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
approvedByGeneralConvention
Indicates that an action, decision, or item has received formal approval from the General Convention.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35521e020819099e72b9e2ccbd36d |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.