Triple
T20946589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saul’s campaign against Amalek |
E515858
|
entity |
| Predicate | includesCommandToDestroy |
P141809
|
FINISHED |
| Object | men |
—
|
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: men | Statement: [Saul’s campaign against Amalek, includesCommandToDestroy, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommandToDestroy Context triple: [Saul’s campaign against Amalek, includesCommandToDestroy, men]
-
A.
canDestroy
Indicates that one entity has the ability or power to destroy another entity.
-
B.
requiresDestructionOrConversionOf
Indicates that one entity can only be fulfilled, resolved, or satisfied if another entity is destroyed or transformed into a different state or form.
-
C.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
D.
possiblyDestroyedIn
Indicates that an entity may have been destroyed during or as a result of a specified event or situation.
-
E.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad97aa48190b4be692e3afce8c9 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:56 p.m.