Triple

T34144222
Position Surface form Disambiguated ID Type / Status
Subject Northern Cheyenne E875803 entity
Predicate leaderInConflict P11563 FINISHED
Object Morning Star (Dull Knife) NE NERFINISHED

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: Morning Star (Dull Knife) | Statement: [Northern Cheyenne, leaderInConflict, Morning Star (Dull Knife)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: leaderInConflict
Context triple: [Northern Cheyenne, leaderInConflict, Morning Star (Dull Knife)]
  • A. belligerentLeader chosen
    Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
  • B. partnerInConflictWith
    Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
  • C. opposingLeaders
    Indicates that two leaders are in opposition to each other, typically representing rival or conflicting sides in a situation or context.
  • D. mainConflict
    Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
  • E. facedConflictOver
    Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
  • 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_69f349aaeef08190a20e72a3fdeb7052 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: May 1, 2026, 1:54 a.m.