Triple
T19753533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian theocracy (Gilead) |
E474443
|
entity |
| Predicate | justifiesPowerBy |
P89146
|
FINISHED |
| Object | divine will |
—
|
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: divine will | Statement: [Christian theocracy (Gilead), justifiesPowerBy, divine will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: justifiesPowerBy Context triple: [Christian theocracy (Gilead), justifiesPowerBy, divine will]
-
A.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
B.
assertedPower
Indicates that one entity has claimed, declared, or exercised authority, control, or dominance over another entity or domain.
-
C.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
D.
usesPoliticalPowerFor
Indicates that an entity employs its political authority or influence to achieve, support, or advance a specified purpose, goal, or outcome.
-
E.
justificationUsedBy
chosen
Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529cae048190b4f8e6ba409bcf8e |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.