Triple
T15531631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Θεόδωρος Κολοκοτρώνης |
E370230
|
entity |
| Predicate | δικάστηκε_για |
P41134
|
FINISHED |
| Object | εσχάτη προδοσία |
—
|
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: εσχάτη προδοσία | Statement: [Θεόδωρος Κολοκοτρώνης, δικάστηκε_για, εσχάτη προδοσία]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: δικάστηκε_για Context triple: [Θεόδωρος Κολοκοτρώνης, δικάστηκε_για, εσχάτη προδοσία]
-
A.
heldCourtIn
Indicates that an authority or governing body formally conducted judicial or official proceedings in a particular place.
-
B.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
C.
heldCourtUnder
Indicates that one authority conducted judicial or ceremonial court proceedings under the jurisdiction, auspices, or authority of another.
-
D.
judgmentInvolves
chosen
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414773548190b3311515f9d957dd |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.