Triple
T21248737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Darius |
E523684
|
entity |
| Predicate | ordersPunishmentOf |
P104230
|
FINISHED |
| Object | accusers of Daniel |
—
|
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: accusers of Daniel | Statement: [King Darius, ordersPunishmentOf, accusers of Daniel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersPunishmentOf Context triple: [King Darius, ordersPunishmentOf, accusers of Daniel]
-
A.
penaltyOrder
chosen
Indicates that an authority has issued a formal decision imposing a penalty or sanction on a party.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
punishedAmong
Indicates that an entity is punished within a particular group or set of entities, as one among them.
-
D.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
E.
punish
Indicates imposing a penalty or negative consequence on an entity in response to its perceived wrongdoing or rule violation.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:56 p.m.