Triple

T38588134
Position Surface form Disambiguated ID Type / Status
Subject Deeprun Tram to Stormwind City E932390 entity
Predicate safeZoneStatus P113069 FINISHED
Object non-combat area 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: non-combat area | Statement: [Deeprun Tram to Stormwind City, safeZoneStatus, non-combat area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safeZoneStatus
Context triple: [Deeprun Tram to Stormwind City, safeZoneStatus, non-combat area]
  • A. hasZoneStatus chosen
    Indicates that a specified zone currently possesses a particular status or condition.
  • B. isProtectedAreaStatus
    Indicates that an entity has a designated protection status, typically signifying legal or formal recognition as a protected area.
  • C. securityBarrierStatus
    Indicates the current operational state or condition of a security barrier (e.g., whether it is active, inactive, open, closed, or otherwise engaged).
  • D. safeHarborStatus
    Indicates that an entity is protected from certain legal, regulatory, or policy liabilities or penalties when specific qualifying conditions are met.
  • E. securityStatus
    Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdaa36f90819093f8661969990c7d completed May 7, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69fcd8fefc588190b063d7ea1ec87b07 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.