Triple
T28090436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juicio a las Juntas |
E709939
|
entity |
| Predicate | assistantProsecutor |
P116234
|
FINISHED |
| Object | Luis Moreno Ocampo |
—
|
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: Luis Moreno Ocampo | Statement: [Juicio a las Juntas, assistantProsecutor, Luis Moreno Ocampo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistantProsecutor Context triple: [Juicio a las Juntas, assistantProsecutor, Luis Moreno Ocampo]
-
A.
prosecutorSought
Indicates that a prosecutor actively pursued or requested a particular legal action, charge, or outcome against a party.
-
B.
helpsProsecute
chosen
Indicates that one entity assists another entity in carrying out a legal prosecution against a target.
-
C.
notableProsecutor
Indicates that the person served as a prosecutor in a way that is widely recognized as significant or noteworthy.
-
D.
subsequentProsecutor
Indicates that one prosecutor follows or succeeds another in handling the same or a related legal case.
-
E.
counselForProsecution
Indicates that an entity serves as a legal representative or advisor acting on behalf of the prosecution in a legal proceeding.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64069d75881908f0e93d1c7c66891 |
completed | May 2, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:58 p.m.