Triple

T20946587
Position Surface form Disambiguated ID Type / Status
Subject Saul’s campaign against Amalek E515858 entity
Predicate hasPrimaryCommand P15534 FINISHED
Object to completely destroy Amalek 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: to completely destroy Amalek | Statement: [Saul’s campaign against Amalek, hasPrimaryCommand, to completely destroy Amalek]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCommand
Context triple: [Saul’s campaign against Amalek, hasPrimaryCommand, to completely destroy Amalek]
  • A. hasCommand chosen
    Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
  • B. containsCommand
    Indicates that one entity includes or embeds a command directed at or executable by another entity.
  • C. hasHigherCommand
    Indicates that one entity holds a superior or higher-level command authority over another entity.
  • D. hasPrimary
    Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
  • E. hasSubordinateCommand
    Indicates that one command or unit holds authority over and directs the operations of another command or unit that is subordinate to it.
  • 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_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.
Created at: April 16, 2026, 12:56 p.m.