Triple
T2932486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioner for Human Rights of the Council of Europe |
E78985
|
entity |
| Predicate | firstHolderEndTime |
P17301
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Commissioner for Human Rights of the Council of Europe, firstHolderEndTime, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderEndTime Context triple: [Commissioner for Human Rights of the Council of Europe, firstHolderEndTime, 2006]
-
A.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
B.
firstHolderEnd
chosen
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
C.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
-
D.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
E.
previousHolderStartDate
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
- 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.