Triple

T29617264
Position Surface form Disambiguated ID Type / Status
Subject Khala E754894 entity
Predicate partiallySeveredIn P167419 FINISHED
Object events of StarCraft II: Legacy of the Void 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: events of StarCraft II: Legacy of the Void | Statement: [Khala, partiallySeveredIn, events of StarCraft II: Legacy of the Void]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partiallySeveredIn
Context triple: [Khala, partiallySeveredIn, events of StarCraft II: Legacy of the Void]
  • A. partlySeveredDuring chosen
    Indicates that an entity was only partially cut or separated during a specified event or time interval.
  • B. partlySeveredBy
    Indicates that one entity is cut, divided, or separated by another entity, but the separation is incomplete or only affects part of it.
  • C. partiallyDestroyed
    Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
  • D. rupturedSegmentOf
    Indicates that one entity is a segment that has undergone rupture and is part of, or derived from, another entity.
  • E. dismembered
    Indicates that one entity has cut or torn another entity’s body into separate parts, typically removing limbs or sections.
  • 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_69f0ef85f62081909842b59fdf8717e1 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
Created at: April 28, 2026, 6:32 p.m.