Triple

T6030882
Position Surface form Disambiguated ID Type / Status
Subject Sunken Road E134298 entity
Predicate aftermathDescription P68859 FINISHED
Object lane filled with Confederate dead 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: lane filled with Confederate dead | Statement: [Sunken Road, aftermathDescription, lane filled with Confederate dead]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aftermathDescription
Context triple: [Sunken Road, aftermathDescription, lane filled with Confederate dead]
  • A. aftermathOf
    Indicates that one event, state, or condition occurs as a consequence or result following another event.
  • B. aftermathPolicy
    Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
  • C. handledAftermathOf
    Indicates that one entity took responsibility for dealing with the consequences or fallout that occurred after another entity’s actions or events.
  • D. after
    Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
  • E. impactOutcome
    Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
  • 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_69c0087515148190a97475d412563865 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c056af89e881909652957f94317684 completed March 22, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69c049e9a68c81909da0cfe4779ce9b5 completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04e8c5bfc8190b986a7071d1b23e3 completed March 22, 2026, 8:18 p.m.
Created at: March 22, 2026, 4:08 p.m.