Triple

T34570487
Position Surface form Disambiguated ID Type / Status
Subject Wallabout Bay burial pits E887610 entity
Predicate victimsAllegiance P58514 FINISHED
Object Continental cause 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: Continental cause | Statement: [Wallabout Bay burial pits, victimsAllegiance, Continental cause]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: victimsAllegiance
Context triple: [Wallabout Bay burial pits, victimsAllegiance, Continental cause]
  • A. belligerentSideOfVictims chosen
    Indicates that the referenced party is the side or faction to which the victims in a conflict or hostile situation belong.
  • B. perpetratorAllegiance
    Indicates that the perpetrator is affiliated with, loyal to, or acting on behalf of a particular group, organization, or cause.
  • C. hasPoliticalAlignmentOfVictims
    Indicates that an entity is associated with victims characterized by a particular political alignment.
  • D. hasVictimNationalities
    Indicates that an event, incident, or action involved victims belonging to one or more specified nationalities.
  • E. notableVictimNationality
    Indicates that the relationship specifies the nationality of a notable victim associated with an event, incident, or action.
  • 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_69f349d1a5fc81908557a46875b2f157 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f727bde8f88190ad746ca515134ca1 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72739c30c81908642eef3feb3afcf completed May 3, 2026, 10:45 a.m.
Created at: May 1, 2026, 2:02 a.m.