Triple

T33811747
Position Surface form Disambiguated ID Type / Status
Subject Battle of Yellow Bayou E866553 entity
Predicate UnionArmyDepartment P103017 FINISHED
Object Department of the Gulf 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: Department of the Gulf | Statement: [Battle of Yellow Bayou, UnionArmyDepartment, Department of the Gulf]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UnionArmyDepartment
Context triple: [Battle of Yellow Bayou, UnionArmyDepartment, Department of the Gulf]
  • A. unionArmyDepartment chosen
    Indicates a relationship where an entity is associated with, assigned to, or operating under a specific department of the Union Army.
  • B. unionArmy
    Indicates that an entity served in, was part of, or is otherwise affiliated with the Union Army (the United States Army of the North) during the American Civil War.
  • C. militaryDepartment
    Indicates that an entity functions as a military-related division, branch, or department within a larger organization or government structure.
  • D. alliedRegiment
    Indicates that one regiment is formally associated or cooperating as an ally with another regiment.
  • E. armyUnion
    Indicates that two or more military forces are joined together into a single unified army or coalition force.
  • 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_69f349911a8c81908478662194b23d8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffcddfc08190bb83e4f2de5bee7b completed May 3, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69f6fc59518081908b0275f47721d561 completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:46 a.m.