Triple

T35318163
Position Surface form Disambiguated ID Type / Status
Subject Battle of Spanish Fort E1019960 entity
Predicate purposeUnion P182728 FINISHED
Object to neutralize Confederate defenses east of Mobile Bay 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 neutralize Confederate defenses east of Mobile Bay | Statement: [Battle of Spanish Fort, purposeUnion, to neutralize Confederate defenses east of Mobile Bay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: purposeUnion
Context triple: [Battle of Spanish Fort, purposeUnion, to neutralize Confederate defenses east of Mobile Bay]
  • A. endedUnionBetween
    Indicates that one entity caused or marked the termination of a union, alliance, or partnership with another entity.
  • B. union
    Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
  • C. unites
    Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
  • D. primaryUnionUnit
    Indicates that an entity serves as the main or principal unit within a union or combined structure.
  • E. primaryUnionObjective
    Indicates the main goal or purpose that a union seeks to achieve in its activities or negotiations.
  • 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_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.
PDg Predicate description generation batch_69f78f629d508190b755848162c4e101 completed May 3, 2026, 6:09 p.m.
Created at: May 3, 2026, 4:03 p.m.