Triple

T19455087
Position Surface form Disambiguated ID Type / Status
Subject Demogorgon (Dungeons & Dragons) E486713 entity
Predicate isBossMonsterFor P126648 FINISHED
Object high-level adventuring parties 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: high-level adventuring parties | Statement: [Demogorgon (Dungeons & Dragons), isBossMonsterFor, high-level adventuring parties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBossMonsterFor
Context triple: [Demogorgon (Dungeons & Dragons), isBossMonsterFor, high-level adventuring parties]
  • A. hasBossType
    Indicates that one entity functions as the superior or boss type in relation to another entity.
  • B. hasOriginBoss
    Indicates that an entity has a specific boss or superior from which it originates or to whom it is hierarchically linked.
  • C. hasBoss
    Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
  • D. notableBoss
    Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
  • E. stageBossOf chosen
    Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
  • 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_69d8e8d86d608190bd199a98d0297f27 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633c2b1108190b492ca23487b91f8 completed April 20, 2026, 2:10 p.m.
PD Predicate disambiguation batch_69e4fd7499a4819082bec0be8afba35c completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:38 p.m.