Triple
T2932470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioner for Human Rights of the Council of Europe |
E78985
|
entity |
| Predicate | canIssueReports |
P2810
|
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: [Commissioner for Human Rights of the Council of Europe, canIssueReports, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIssueReports Context triple: [Commissioner for Human Rights of the Council of Europe, canIssueReports, true]
-
A.
canReport
chosen
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
-
B.
requiresReportFrom
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
C.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
-
D.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
-
E.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983a4ae08190aa1aeb2747abd1a1 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.