Triple

T35013890
Position Surface form Disambiguated ID Type / Status
Subject Planemeld crisis E1010001 entity
Predicate involvedDaedricPrince P195512 FINISHED
Object Molag Bal 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: Molag Bal | Statement: [Planemeld crisis, involvedDaedricPrince, Molag Bal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: involvedDaedricPrince
Context triple: [Planemeld crisis, involvedDaedricPrince, Molag Bal]
  • A. patronDaedra
    Indicates that one entity serves as the patron Daedra (a guiding or sponsoring Daedric power) of another entity.
  • B. valarInvolved
    Indicates that one or more Valar are involved in, participate in, or are associated with the specified event, action, or relationship.
  • C. powerBehindThrone
    Indicates a relationship where one entity secretly or informally controls or strongly influences the authority and decisions of another entity that holds the official position of power.
  • D. coPrince
    Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
  • E. Listoghil
    Indicates a relationship in which an entity is associated with or belongs to the place or context referred to as Listoghil.
  • F. None of above. chosen

Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fdd5fba5048190b7d430ae2054a1fd completed May 8, 2026, 12:24 p.m.
PD Predicate disambiguation batch_69fdd35f76f88190a1854ea27132f9c7 completed May 8, 2026, 12:13 p.m.
PDg Predicate description generation batch_69fdd5faea908190a17d77e050362ef5 completed May 8, 2026, 12:24 p.m.
Created at: May 3, 2026, 4:01 p.m.