Triple

T6149479
Position Surface form Disambiguated ID Type / Status
Subject Petersburg was a major railroad hub supplying Richmond E137160 entity
Predicate consequenceOfLoss P812 FINISHED
Object severing of Confederate supply lines to Richmond 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: severing of Confederate supply lines to Richmond | Statement: [Petersburg was a major railroad hub supplying Richmond, consequenceOfLoss, severing of Confederate supply lines to Richmond]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfLoss
Context triple: [Petersburg was a major railroad hub supplying Richmond, consequenceOfLoss, severing of Confederate supply lines to Richmond]
  • A. consequenceOfDestruction
    Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
  • B. causedLossOf
    Indicates that one entity brought about or was responsible for another entity experiencing a loss.
  • C. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • D. significantLoss
    Indicates that an entity has experienced a major or substantial decrease in value, quantity, or status beyond a normal or minor loss.
  • E. consequenceOfRevocation
    Indicates that something occurs as a direct result of a prior revocation event or decision.
  • 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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05ce21820819096be9159d6b70a5f completed March 22, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69c055f39e0881909ae56444b1b48929 completed March 22, 2026, 8:49 p.m.
Created at: March 22, 2026, 4:16 p.m.