Triple
T21248720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Darius |
E523684
|
entity |
| Predicate | condemnationMethod |
P143364
|
FINISHED |
| Object | throwing Daniel into the lions’ den |
—
|
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: throwing Daniel into the lions’ den | Statement: [King Darius, condemnationMethod, throwing Daniel into the lions’ den]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condemnationMethod Context triple: [King Darius, condemnationMethod, throwing Daniel into the lions’ den]
-
A.
condemnation
Indicates that an entity expresses strong disapproval or denunciation of another entity, action, or situation.
-
B.
condemnationReason
Indicates the reason or grounds for which something or someone is condemned or judged negatively.
-
C.
condemnedUse
Indicates that one entity has formally disapproved, denounced, or prohibited the use of another entity.
-
D.
condemnedIn
Indicates that an entity was formally denounced, sentenced, or declared guilty within a particular place, context, or proceeding.
-
E.
condemnedAs
Indicates that one entity formally or strongly denounces another entity by labeling it as wrong, guilty, or unacceptable.
- 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_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. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:56 p.m.