Triple

T30877173
Position Surface form Disambiguated ID Type / Status
Subject A2100-derived GPS III bus E786508 entity
Predicate supportsSignal GENERATED
Object L1C civil signal UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsSignal
Context triple: [A2100-derived GPS III bus, supportsSignal, L1C civil signal]
  • A. supportsReach
    Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
  • B. usesSignaling
    Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
  • C. supportsInstrument
    Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
  • D. compatibleWithSignaling chosen
    Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by another entity.
  • E. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • F. None of above.

Provenance (1 batch)

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_69f224bae17c8190bb3a6a28e3d019df completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:48 p.m.