Triple
T8259837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenian court |
E193165
|
entity |
| Predicate | jurySelectionMethod |
P81249
|
FINISHED |
| Object | sortition |
—
|
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: sortition | Statement: [Athenian court, jurySelectionMethod, sortition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurySelectionMethod Context triple: [Athenian court, jurySelectionMethod, sortition]
-
A.
judgesSelectionMethod
Indicates that a judge or judging body uses a particular method or criteria to evaluate and select among options or candidates.
-
B.
juryProvidedBy
Indicates that a particular jury is supplied, appointed, or made available by a specified source or authority.
-
C.
usesJuries
Indicates that a legal system, court, or process employs juries to participate in deciding cases or determining outcomes.
-
D.
juryComposition
Indicates the relationship specifying how a jury is constituted, including the number, type, or characteristics of its members.
-
E.
judgeSelectionAuthority
Indicates that an entity has the authority or responsibility to select, appoint, or choose judges for a given role or position.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793479d08190bd0dd8740bebff95 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.