Triple

T29654684
Position Surface form Disambiguated ID Type / Status
Subject Aiur E750233 entity
Predicate partiallyOverrunBy P85045 FINISHED
Object Zerg 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: Zerg | Statement: [Aiur, partiallyOverrunBy, Zerg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partiallyOverrunBy
Context triple: [Aiur, partiallyOverrunBy, Zerg]
  • A. isPartially
    Indicates that one entity is included within another to some extent, but not completely or fully.
  • B. partiallyOn
    Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
  • C. overriddenInPartBy
    Indicates that one item’s provisions or effects are partially superseded or modified by another item.
  • D. eventuallyOverrunBy chosen
    Indicates that one entity is ultimately defeated, overwhelmed, or taken over by another entity or force after some passage of time.
  • E. holdsOver
    Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
  • 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_69f0d6226fe881908819197c9ef9ee04 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
Created at: April 28, 2026, 6:54 p.m.