Triple
T32608987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly Resolution 3485 |
E833601
|
entity |
| Predicate | condemnsActionBy |
P174646
|
FINISHED |
| Object | Indonesia |
—
|
NE NERFINISHED |
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: Indonesia | Statement: [UN General Assembly Resolution 3485, condemnsActionBy, Indonesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condemnsActionBy Context triple: [UN General Assembly Resolution 3485, condemnsActionBy, Indonesia]
-
A.
condemnedAction
Indicates that an entity has formally expressed strong disapproval of, or issued a denunciation against, a particular action.
-
B.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
C.
condemnsReluctantly
Indicates that an entity expresses disapproval or issues a condemnation of another entity or action, but does so with hesitation, regret, or unwillingness.
-
D.
condemnedAs
Indicates that one entity formally or strongly denounces another entity by labeling it as wrong, guilty, or unacceptable.
-
E.
aimOfCondemnation
Indicates that an act of condemnation is directed toward a particular target or objective.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c91a1c819097d51d2a159e223b |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:05 a.m.