Triple
T37470067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbiter |
E931130
|
entity |
| Predicate | judgmentBasis |
P59235
|
FINISHED |
| Object | the totality of a soul’s actions and choices |
—
|
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: the totality of a soul’s actions and choices | Statement: [Arbiter, judgmentBasis, the totality of a soul’s actions and choices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgmentBasis Context triple: [Arbiter, judgmentBasis, the totality of a soul’s actions and choices]
-
A.
decisionBasis
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
B.
reasonForJudgment
chosen
Indicates that a particular reason, basis, or justification underlies or explains a given judgment or decision.
-
C.
judgmentResult
Indicates the outcome or decision produced by a judgment, such as a court ruling, evaluation, or formal assessment, regarding the entities involved.
-
D.
judgeFrom
Indicates that one entity forms an opinion, evaluation, or conclusion about something based on another specified source, basis, or perspective.
-
E.
judgmentContext
Indicates the situational, legal, or evaluative framework within which a judgment or decision is made.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e3c8e248190b4a4067b9262c845 |
completed | May 6, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.