Triple
T934838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esther |
E20171
|
entity |
| Predicate | containsDecree |
P21747
|
FINISHED |
| Object | Royal edict against the Jews |
—
|
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: Royal edict against the Jews | Statement: [Esther, containsDecree, Royal edict against the Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDecree Context triple: [Esther, containsDecree, Royal edict against the Jews]
-
A.
awardedByDecreeOf
Indicates that something (such as a title, right, or benefit) is formally granted or conferred through an official decree or authoritative order.
-
B.
numberOfEdicts
Indicates the total count of edicts associated with or issued by a given entity.
-
C.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
D.
thirdEdictContent
Indicates the specific directive, rule, or message expressed in the third edict of a defined set of edicts.
-
E.
recognizedAsOrdinanceBy
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.