Triple

T25865073
Position Surface form Disambiguated ID Type / Status
Subject Mine Run Campaign E651587 entity
Predicate reasonForUnionWithdrawal P12349 FINISHED
Object strong Confederate fortifications 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: strong Confederate fortifications | Statement: [Mine Run Campaign, reasonForUnionWithdrawal, strong Confederate fortifications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForUnionWithdrawal
Context triple: [Mine Run Campaign, reasonForUnionWithdrawal, strong Confederate fortifications]
  • A. reasonForWithdrawal chosen
    Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
  • B. reasonForDisbandment
    Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
  • C. withdrewFrom
    Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
  • D. expulsionReason
    Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
  • E. reasonForAnnulment
    Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
  • 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_69e7ab3a199c81909227cb964cacfe24 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f67c9fe7b48190b79b4041357edb49 completed May 2, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69f678cc272081909e5c70f1bc7407f0 completed May 2, 2026, 10:21 p.m.
Created at: April 22, 2026, 8:07 a.m.