Triple
T1352333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trial of God |
E28908
|
entity |
| Predicate | questionedConcept |
P3648
|
FINISHED |
| Object | God’s justice |
—
|
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: God’s justice | Statement: [The Trial of God, questionedConcept, God’s justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionedConcept Context triple: [The Trial of God, questionedConcept, God’s justice]
-
A.
challengedConcept
chosen
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
B.
philosophicalConcept
Indicates that one entity is a philosophical concept that characterizes, explains, or is thematically central to the other entity.
-
C.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
D.
theologicalConcept
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
E.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26d0c4481908fddda89242a57b3 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.