Triple

T38311926
Position Surface form Disambiguated ID Type / Status
Subject Romulan–Klingon conflicts E1033710 entity
Predicate factionGoalKlingon P182797 FINISHED
Object assert military honor and dominance 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: assert military honor and dominance | Statement: [Romulan–Klingon conflicts, factionGoalKlingon, assert military honor and dominance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: factionGoalKlingon
Context triple: [Romulan–Klingon conflicts, factionGoalKlingon, assert military honor and dominance]
  • A. goalOfFactions chosen
    Indicates that a particular objective or aim is associated with, pursued by, or belongs to one or more factions.
  • B. conflictGoal
    Indicates a relationship where one entity’s goal is incompatible with, obstructs, or opposes another entity’s goal.
  • C. antiTreatyFactionGoal
    Indicates that an entity’s goal is to oppose, undermine, or prevent the implementation of a particular treaty or agreement.
  • D. goalDuringWar
    Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
  • E. goalOfRebelSide
    Indicates that the specified goal is pursued or held by the rebel side in a conflict or opposition scenario.
  • 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_69f76e132c408190969b3d35c04b87ae completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd553d7cb881908d243e7a9f30ac85 completed May 8, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69fd514dcb1c81908333c70d7edd79c9 completed May 8, 2026, 2:58 a.m.
Created at: May 3, 2026, 4:30 p.m.