Triple
T24714996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacto de San José |
E612134
|
entity |
| Predicate | permiteCompetenciaCorteIDH |
P157192
|
FINISHED |
| Object | previa aceptación por el Estado |
—
|
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: previa aceptación por el Estado | Statement: [Pacto de San José, permiteCompetenciaCorteIDH, previa aceptación por el Estado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permiteCompetenciaCorteIDH Context triple: [Pacto de San José, permiteCompetenciaCorteIDH, previa aceptación por el Estado]
-
A.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
B.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
C.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
D.
competencia
Indicates that one entity is in a state of competition or rivalry with another, typically striving to achieve a similar goal or advantage.
-
E.
supportsCompetitionParticipationOf
Indicates that one entity provides assistance, resources, or endorsement enabling another entity to take part in a competition.
- F. None of above. chosen
Provenance (4 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 3:33 a.m.