Triple

T36196854
Position Surface form Disambiguated ID Type / Status
Subject Battle between USS Constitution and HMS Java E1047150 entity
Predicate casualtiesUnitedStatesWounded P824 FINISHED
Object 26 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: 26 | Statement: [Battle between USS Constitution and HMS Java, casualtiesUnitedStatesWounded, 26]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesUnitedStatesWounded
Context triple: [Battle between USS Constitution and HMS Java, casualtiesUnitedStatesWounded, 26]
  • A. casualtiesWoundedUS chosen
    Indicates that the relationship specifies the number of U.S. individuals who were wounded as casualties in an event or incident.
  • B. casualtiesUnitedStates
    Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
  • C. UScasualties
    Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
  • D. casualtiesWounded
    Indicates that an event or situation resulted in people being injured but not killed.
  • E. casualtiesUnionWounded
    Indicates that the number of casualties specifically refers to Union forces who were wounded.
  • 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_69f76e414bdc8190996f15a544220a3d completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba6d06f48190a71b5a2f19e2232f completed May 3, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:08 p.m.