Triple
T25322839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACHPR |
E634929
|
entity |
| Predicate | hasSpecialMechanism |
P32672
|
FINISHED |
| Object | Special Rapporteurs |
—
|
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: Special Rapporteurs | Statement: [ACHPR, hasSpecialMechanism, Special Rapporteurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialMechanism Context triple: [ACHPR, hasSpecialMechanism, Special Rapporteurs]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
haveHighLevelMechanism
Indicates that an entity possesses or is associated with a high-level, abstract mechanism explaining how something works or occurs.
-
C.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
D.
hasSpecial
chosen
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:29 p.m.