Triple

T23399
Position Surface form Disambiguated ID Type / Status
Subject Battles of Lexington and Concord E464 entity
Predicate casualtiesAndLosses P661 FINISHED
Object British over 250 killed, wounded, or missing 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: British over 250 killed, wounded, or missing | Statement: [Battles of Lexington and Concord, casualtiesAndLosses, British over 250 killed, wounded, or missing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesAndLosses
Context triple: [Battles of Lexington and Concord, casualtiesAndLosses, British over 250 killed, wounded, or missing]
  • A. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • B. casualtiesEstimate chosen
    Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
  • C. casualtiesJapan
    Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
  • D. casualtiesUnitedStates
    Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
  • E. casualtiesKilledUS
    Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
  • 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_69a243b4ac2c8190b93c303df797b7b2 completed Feb. 28, 2026, 1:24 a.m.
NER Named-entity recognition batch_69a246e94ca881908f7a7d2c0b293033 completed Feb. 28, 2026, 1:37 a.m.
PD Predicate disambiguation batch_69a246560af88190961ea00b35cf9388 completed Feb. 28, 2026, 1:35 a.m.
Created at: Feb. 28, 2026, 1:34 a.m.