Triple

T22732259
Position Surface form Disambiguated ID Type / Status
Subject Morgan's Raid of 1863 E562164 entity
Predicate violatedOrderDetail P29586 FINISHED
Object crossed the Ohio River against orders 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: crossed the Ohio River against orders | Statement: [Morgan's Raid of 1863, violatedOrderDetail, crossed the Ohio River against orders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: violatedOrderDetail
Context triple: [Morgan's Raid of 1863, violatedOrderDetail, crossed the Ohio River against orders]
  • A. violationOf chosen
    Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
  • B. penaltyOrder
    Indicates that an authority has issued a formal decision imposing a penalty or sanction on a party.
  • C. violationContext
    Indicates the specific circumstances, conditions, or situational factors under which a violation occurs or is considered to have occurred.
  • D. violatedPrinciple
    Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
  • E. allegedViolationSystem
    Indicates a system is reported or suspected to have violated a rule, policy, or regulation, without the violation being legally or formally established.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1792ef5bc819088af71bdc96ed41b completed April 29, 2026, 3:21 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:21 p.m.