Triple
T4922576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pillar of Severity |
E110499
|
entity |
| Predicate | GevurahRole |
P5518
|
FINISHED |
| Object | strength and judgment |
—
|
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: strength and judgment | Statement: [Pillar of Severity, GevurahRole, strength and judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GevurahRole Context triple: [Pillar of Severity, GevurahRole, strength and judgment]
-
A.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
B.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
C.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
regnalRole
Indicates the specific official capacity or position a monarch holds or held during their reign.
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.