Triple

T19837507
Position Surface form Disambiguated ID Type / Status
Subject Benaiah E476635 entity
Predicate weaponUsedAgainstEgyptian P22414 FINISHED
Object Egyptian’s own spear 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: Egyptian’s own spear | Statement: [Benaiah, weaponUsedAgainstEgyptian, Egyptian’s own spear]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: weaponUsedAgainstEgyptian
Context triple: [Benaiah, weaponUsedAgainstEgyptian, Egyptian’s own spear]
  • A. weaponUsedAgainst chosen
    Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
  • B. opponentAtBattleOfTheNile
    Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
  • C. combatantStrengthEgyptian
    Indicates that the entity has combatant strength or military capability associated with Egyptian forces or context.
  • D. associatedWithPharaoh
    Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
  • E. weaponsUsed
    Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
  • 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65802f57081909e4e94694684bda4 completed April 20, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69e5305bda388190a23b7191768107b1 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:50 p.m.