Triple

T30023362
Position Surface form Disambiguated ID Type / Status
Subject Phoenix (StarCraft) E762810 entity
Predicate microRequirement P168363 FINISHED
Object high 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 | Statement: [Phoenix (StarCraft), microRequirement, high]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: microRequirement
Context triple: [Phoenix (StarCraft), microRequirement, high]
  • A. maintenanceRequirement
    Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
  • B. typicalRequirement
    Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
  • C. mayIncludeRequirement
    Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
  • D. noticeRequirement
    Indicates that one party is obligated to provide advance notification to another party before a specified action, change, or event occurs.
  • E. minimumExistenceRequirement
    Indicates that there is a lowest threshold or baseline level of existence or presence that must be met for the related condition, entity, or relationship to hold.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f679a8f07c8190bcde0b1bf2a9427a completed May 2, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69f66ec9919881908a187bfc7c4df192 completed May 2, 2026, 9:38 p.m.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 29, 2026, 6:48 p.m.