Triple
T19161814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expert Mechanism on the Rights of Indigenous Peoples |
E469073
|
entity |
| Predicate | membersSelectedOnBasisOf |
P23142
|
FINISHED |
| Object | expertise |
—
|
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: expertise | Statement: [Expert Mechanism on the Rights of Indigenous Peoples, membersSelectedOnBasisOf, expertise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersSelectedOnBasisOf Context triple: [Expert Mechanism on the Rights of Indigenous Peoples, membersSelectedOnBasisOf, expertise]
-
A.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
C.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
D.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebe03ac8190bbe0b34ebf0d90c6 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.