Triple

T24503098
Position Surface form Disambiguated ID Type / Status
Subject Third Corps, Army of Northern Virginia E617989 entity
Predicate sideOpposed P36358 FINISHED
Object United States (Union) 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: United States (Union) | Statement: [Third Corps, Army of Northern Virginia, sideOpposed, United States (Union)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sideOpposed
Context triple: [Third Corps, Army of Northern Virginia, sideOpposed, United States (Union)]
  • A. positionOpposed
    Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
  • B. hasOpposingSide chosen
    Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
  • C. opposingCommanderSide
    Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
  • D. secondaryOpponent
    Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
  • E. opponentCommanderSide
    Indicates that one commander is positioned on the opposing side relative to another commander in a conflict or competitive scenario.
  • 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_69e2d7f682108190a1a7ca5fd485ee8a completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2a9d912e88190bc39c05a9d7f407e completed April 30, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69f2a6a4580481908fddc385f5262f95 completed April 30, 2026, 12:47 a.m.
Created at: April 18, 2026, 2:23 a.m.