Triple

T17518498
Position Surface form Disambiguated ID Type / Status
Subject Amarr Empire E426625 entity
Predicate notableConflict P1406 FINISHED
Object Amarr-Minmatar conflict NE NERFINISHED

How this triple was built (3 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: Amarr-Minmatar conflict | Statement: [Amarr Empire, notableConflict, Amarr-Minmatar conflict]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amarr-Minmatar conflict
Context triple: [Amarr Empire, notableConflict, Amarr-Minmatar conflict]
  • A. Battle of Veridian III
    The Battle of Veridian III is a pivotal Star Trek: The Next Generation conflict in which the crew confronts Dr. Tolian Soran’s plan to destroy a star, leading to Captain Kirk’s death and the loss of the Enterprise-D.
  • B. Ferrix uprising
    The Ferrix uprising is a pivotal rebellion on the planet Ferrix in the Star Wars series *Andor*, where local residents rise up against Imperial oppression.
  • C. Xindi conflict
    The Xindi conflict is a major storyline in Star Trek: Enterprise depicting humanity’s tense and complex struggle with the multi-species Xindi following a devastating attack on Earth.
  • D. Romulan–Klingon conflicts
    The Romulan–Klingon conflicts are a series of recurring wars and skirmishes between the Romulan Star Empire and the Klingon Empire in the Star Trek universe, marked by shifting alliances, espionage, and territorial disputes.
  • E. Battle of Wolf 359
    The Battle of Wolf 359 is a pivotal Star Trek: The Next Generation conflict in which a Borg cube devastates a Federation fleet, profoundly shaping the series’ portrayal of the Borg threat and Captain Picard’s character.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Amarr-Minmatar conflict
Target entity description: The Amarr–Minmatar conflict is a central, long-running interstellar war in the EVE Online universe, rooted in the Amarr Empire’s historic enslavement and oppression of the Minmatar people.
  • A. Battle of Veridian III
    The Battle of Veridian III is a pivotal Star Trek: The Next Generation conflict in which the crew confronts Dr. Tolian Soran’s plan to destroy a star, leading to Captain Kirk’s death and the loss of the Enterprise-D.
  • B. Ferrix uprising
    The Ferrix uprising is a pivotal rebellion on the planet Ferrix in the Star Wars series *Andor*, where local residents rise up against Imperial oppression.
  • C. Xindi conflict
    The Xindi conflict is a major storyline in Star Trek: Enterprise depicting humanity’s tense and complex struggle with the multi-species Xindi following a devastating attack on Earth.
  • D. Romulan–Klingon conflicts
    The Romulan–Klingon conflicts are a series of recurring wars and skirmishes between the Romulan Star Empire and the Klingon Empire in the Star Trek universe, marked by shifting alliances, espionage, and territorial disputes.
  • E. Battle of Wolf 359
    The Battle of Wolf 359 is a pivotal Star Trek: The Next Generation conflict in which a Borg cube devastates a Federation fleet, profoundly shaping the series’ portrayal of the Borg threat and Captain Picard’s character.
  • F. None of above. chosen

Provenance (2 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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452d0daa48190be69aff32b0324bc completed April 19, 2026, 3:58 a.m.
Created at: April 10, 2026, 5:49 a.m.