Triple
T9606568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Council resolutions |
E231984
|
entity |
| Predicate | oftenCallOn |
P2350
|
FINISHED |
| Object | States to implement recommendations |
—
|
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: States to implement recommendations | Statement: [Human Rights Council resolutions, oftenCallOn, States to implement recommendations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCallOn Context triple: [Human Rights Council resolutions, oftenCallOn, States to implement recommendations]
-
A.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
B.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
C.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
D.
callsFor
chosen
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
oftenSoughtOn
Indicates that one entity is frequently searched for, requested, or pursued in relation to another entity.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a6006d48190adc03306533b9be6 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.