Triple
T25161617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistema Interamericano de Derechos Humanos |
E626453
|
entity |
| Predicate | tieneÓrganoRelacionado |
P65107
|
FINISHED |
| Object | Secretaría General de la OEA |
—
|
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: Secretaría General de la OEA | Statement: [Sistema Interamericano de Derechos Humanos, tieneÓrganoRelacionado, Secretaría General de la OEA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneÓrganoRelacionado Context triple: [Sistema Interamericano de Derechos Humanos, tieneÓrganoRelacionado, Secretaría General de la OEA]
-
A.
имеетОрган
chosen
Indicates that one entity possesses or contains a specific organ as a part of its body.
-
B.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
-
C.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
D.
hasOrganPart
Indicates that one entity includes another entity as a constituent organ or anatomical part.
-
E.
mayHaveOrgan
Indicates that an entity is allowed or permitted to possess or contain a particular organ.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:31 a.m.