Triple

T35318160
Position Surface form Disambiguated ID Type / Status
Subject Battle of Spanish Fort E1019960 entity
Predicate offensiveCommander P817 FINISHED
Object Edward Canby NE NERFINISHED

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: Edward Canby | Statement: [Battle of Spanish Fort, offensiveCommander, Edward Canby]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offensiveCommander
Context triple: [Battle of Spanish Fort, offensiveCommander, Edward Canby]
  • A. opposingCommander
    Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
  • B. commanderAttacker
    Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
  • C. operationalCommanderAttacker chosen
    Indicates that the subject serves as the operational commander directing and controlling the attacking forces in the described action or event.
  • D. commanderOfVictoriousSide
    Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
  • E. opponentCommanderAttacker
    Indicates that the referenced commander is the opposing side’s commander who is initiating or carrying out an attack.
  • 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_69f76de9d45c81908a2ed0956b448b65 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f790941e8c8190aefdb9ecdaffb937 completed May 3, 2026, 6:14 p.m.
PD Predicate disambiguation batch_69f78e2f52e08190a77661223a96c601 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:03 p.m.