Triple

T17359559
Position Surface form Disambiguated ID Type / Status
Subject X-band E422030 entity
Predicate typicalApplicationEnvironment P72813 FINISHED
Object space-to-Earth links 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: space-to-Earth links | Statement: [X-band, typicalApplicationEnvironment, space-to-Earth links]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalApplicationEnvironment
Context triple: [X-band, typicalApplicationEnvironment, space-to-Earth links]
  • A. typicalApplicationWindow
    Indicates that something is a standard or commonly used application window in a software environment.
  • B. primaryOperatingEnvironment
    Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
  • C. typicalPlatform
    Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
  • D. environmentType
    Indicates the kind or category of environment associated with an entity or situation.
  • E. appliesToOperationalEnvironment chosen
    Indicates that something (such as a rule, requirement, or condition) is relevant to, valid in, or specifically intended for a particular operational environment.
  • 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_69d889d520008190a26917a95bf1c2ea completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a4be7448190988593ee342348c1 completed April 19, 2026, 2:13 a.m.
PD Predicate disambiguation batch_69e3b02662d08190a07d0fb5c04b6f33 completed April 18, 2026, 4:24 p.m.
Created at: April 10, 2026, 5:44 a.m.