Triple

T16308822
Position Surface form Disambiguated ID Type / Status
Subject Battle of Fort Stevens E395991 entity
Predicate AbrahamLincolnRisk P59284 FINISHED
Object came under Confederate sharpshooter fire 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: came under Confederate sharpshooter fire | Statement: [Battle of Fort Stevens, AbrahamLincolnRisk, came under Confederate sharpshooter fire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AbrahamLincolnRisk
Context triple: [Battle of Fort Stevens, AbrahamLincolnRisk, came under Confederate sharpshooter fire]
  • A. AlexanderRisk
    Indicates a relationship where Alexander is exposed to, associated with, or responsible for a particular risk or potential adverse outcome.
  • B. riskBasis
    Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
  • C. riskTaken chosen
    Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
  • D. riskElement
    Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
  • E. riskType
    Indicates the category or nature of risk associated with an entity, event, or relationship.
  • 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_69d87f23bb088190a16fbb91a1957ea5 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e288d776808190a7c9918477f07216 completed April 17, 2026, 7:24 p.m.
PD Predicate disambiguation batch_69e219fa5508819097e9d383348bf174 completed April 17, 2026, 11:31 a.m.
Created at: April 10, 2026, 5:06 a.m.