Triple

T20667658
Position Surface form Disambiguated ID Type / Status
Subject Battle of Stadtlohn E507933 entity
Predicate belligerentReligionProtestantSide P137031 FINISHED
Object Protestant 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: Protestant | Statement: [Battle of Stadtlohn, belligerentReligionProtestantSide, Protestant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belligerentReligionProtestantSide
Context triple: [Battle of Stadtlohn, belligerentReligionProtestantSide, Protestant]
  • A. hasReligionOfBelligerents chosen
    Indicates that the belligerent parties in a conflict are associated with a particular religion or religious affiliation.
  • B. belligerentAgainst
    Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
  • C. conflictBelligerent
    Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
  • D. belligerentFor
    Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
  • E. statusInMainlineProtestantism
    Indicates the recognized standing, role, or level of acceptance an entity has within mainline Protestant Christian traditions.
  • 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_69e0b4c059bc81908ea762cd73ea4424 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b5c4c4608190ae17da4a59e5ae80 completed April 20, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69e5c03caee881908be4dd25796a03d5 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 11:44 a.m.