Triple

T37552429
Position Surface form Disambiguated ID Type / Status
Subject Tomb of Sargeras E933617 entity
Predicate secondaryEnemyType P15619 FINISHED
Object Naga 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: Naga | Statement: [Tomb of Sargeras, secondaryEnemyType, Naga]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryEnemyType
Context triple: [Tomb of Sargeras, secondaryEnemyType, Naga]
  • A. primaryEnemy
    Indicates that one entity is the main or most significant adversary or opponent of another entity.
  • B. enemyType chosen
    Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
  • C. secondaryOpponent
    Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
  • D. secondaryProtagonistType
    Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
  • E. enemyTypeOpposed
    Indicates that one type of enemy is defined as being in opposition or conflict with another enemy type.
  • 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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff97637ad881908c24fe2cc6b036db completed May 9, 2026, 8:21 p.m.
PD Predicate disambiguation batch_69ff96c43a808190942eeda1934602db completed May 9, 2026, 8:19 p.m.
Created at: May 3, 2026, 4:17 p.m.