Triple

T37164050
Position Surface form Disambiguated ID Type / Status
Subject ISDB E920747 entity
Predicate supportsEmergencyWarningSystem P86231 FINISHED
Object true 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: true | Statement: [ISDB, supportsEmergencyWarningSystem, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsEmergencyWarningSystem
Context triple: [ISDB, supportsEmergencyWarningSystem, true]
  • A. supportsEmergencyAlertingEnhancements chosen
    Indicates that an entity provides or enables additional capabilities or improvements specifically for emergency alerting functions.
  • B. supportsEmergencySOS
    Indicates that one entity provides or is compatible with an emergency SOS function or service for another entity.
  • C. supportsAlarm
    Indicates that one entity is capable of handling, enabling, or being compatible with an alarm feature or functionality for another entity.
  • D. supportsCivilAuthorities
    Indicates that one entity provides assistance, endorsement, or backing to civil authorities in performing their roles or exercising their powers.
  • E. supportsEmergencySOSViaSatellite
    Indicates that an entity provides or is compatible with emergency SOS communication functionality using satellite connectivity.
  • 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_69f76ea0429081908c711b55599eac3c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037c8e2c648190a65fc9c7872861af completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a11efc08190bb7cacc1325b4dc6 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:15 p.m.