Triple
T28090462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juicio a las Juntas |
E709939
|
entity |
| Predicate | numberOfVictimCasesHeard |
P11610
|
FINISHED |
| Object | around 700 |
—
|
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: around 700 | Statement: [Juicio a las Juntas, numberOfVictimCasesHeard, around 700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVictimCasesHeard Context triple: [Juicio a las Juntas, numberOfVictimCasesHeard, around 700]
-
A.
numberOfVictimsClaimedInTestimony
Indicates the quantity of victims that a person asserts or reports in their testimony.
-
B.
numberOfCases
chosen
Indicates the total count of individual instances, occurrences, or records associated with a particular situation, condition, or category.
-
C.
numberOfVictimsClaimed
Indicates the reported count of victims associated with a particular event, incident, or action.
-
D.
hearCasesBroughtBy
Indicates that a judicial body or authority formally considers and adjudicates legal cases initiated by a particular party or group.
-
E.
heardCasesInvolving
Indicates that a judicial body or decision-maker has formally considered and adjudicated legal cases concerning a particular party, issue, or subject matter.
- 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_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 27, 2026, 8:58 p.m.