Triple
T30463202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asha |
E775065
|
entity |
| Predicate | roleInJudgment |
P199930
|
FINISHED |
| Object | criterion for judging souls |
—
|
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: criterion for judging souls | Statement: [Asha, roleInJudgment, criterion for judging souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJudgment Context triple: [Asha, roleInJudgment, criterion for judging souls]
-
A.
roleInJudges
Indicates that an entity holds or held a specific role, position, or function within a judicial body or among a group of judges.
-
B.
juryRole
Indicates that an entity serves in the capacity or function of a juror within a judicial or decision-making process.
-
C.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
D.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
E.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: April 29, 2026, 8:10 p.m.