Triple
T4886782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dike (justice) as divine order |
E109458
|
entity |
| Predicate | isSanctionedBy |
P59651
|
FINISHED |
| Object | the gods |
—
|
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 gods | Statement: [Dike (justice) as divine order, isSanctionedBy, the gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSanctionedBy Context triple: [Dike (justice) as divine order, isSanctionedBy, the gods]
-
A.
canBeSanctionedFor
Indicates that an entity is subject to penalties or disciplinary measures as a consequence of a specified action, behavior, or condition.
-
B.
typeOfSanction
Indicates the specific category or kind of sanction that is applied in a given situation.
-
C.
receivedSanctionFrom
Indicates that one entity has been subjected to a formal penalty, restriction, or disciplinary measure imposed by another entity.
-
D.
countrySubjectToSanctions
Indicates that a country is currently facing formal sanctions or restrictive measures imposed by another state or international body.
-
E.
canImposeSanctions
Indicates that one entity has the authority or power to apply punitive or restrictive measures (sanctions) against another entity.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e03a7fc8190bcac63f4b19e586e |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6d5976a081909090c0c263f6e9b7 |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:28 p.m.