Triple
T24714973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacto de San José |
E612134
|
entity |
| Predicate | reconoceDerecho |
P3079
|
FINISHED |
| Object | derecho a la vida |
—
|
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: derecho a la vida | Statement: [Pacto de San José, reconoceDerecho, derecho a la vida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconoceDerecho Context triple: [Pacto de San José, reconoceDerecho, derecho a la vida]
-
A.
rightsRecognizedIn
Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
-
B.
ramaDelDerecho
Indicates a classification relationship where a legal concept or norm belongs to, or is categorized under, a specific branch of law.
-
C.
legalidad recuperada
Indicates that a previously lost or suspended legal status, order, or compliance has been restored.
-
D.
recognizedRight
chosen
Indicates that an agent formally acknowledges and accepts that another party possesses a specific right or entitlement.
-
E.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 3:33 a.m.