Triple

T37456752
Position Surface form Disambiguated ID Type / Status
Subject Infestor E930818 entity
Predicate abilityType_InfestedTerrans P187857 FINISHED
Object summon temporary units 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: summon temporary units | Statement: [Infestor, abilityType_InfestedTerrans, summon temporary units]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: abilityType_InfestedTerrans
Context triple: [Infestor, abilityType_InfestedTerrans, summon temporary units]
  • A. InfestedTerrans_effect chosen
    Indicates that an effect is applied or triggered by Infested Terrans, typically representing the outcome of their attack or presence.
  • B. abilityType_NeuralParasite
    Indicates a relationship where one entity uses a neural parasite ability to mentally control or dominate another entity.
  • C. isInfestedWith
    Indicates that one entity is overrun, occupied, or contaminated by another, typically unwanted, organism or agent.
  • D. isAvailableToAllZergSubfactions
    Indicates that something can be accessed or used by every Zerg subfaction without restriction.
  • E. signOfInfestation
    Indicates that one entity serves as evidence or indication that another entity is infested or experiencing an infestation.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbacaf54648190811ea33b34907e8e completed May 6, 2026, 9:03 p.m.
PD Predicate disambiguation batch_69fba883f770819091059c6f6c6af9f7 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:17 p.m.