Triple

T4170496
Position Surface form Disambiguated ID Type / Status
Subject Saorview E84549 entity
Predicate coverageCharacteristic P14568 FINISHED
Object line-of-sight dependent reception 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: line-of-sight dependent reception | Statement: [Saorview, coverageCharacteristic, line-of-sight dependent reception]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coverageCharacteristic
Context triple: [Saorview, coverageCharacteristic, line-of-sight dependent reception]
  • A. altitudeCoverageCharacteristic
    Indicates the range or specific values of altitude over which something (such as a system, sensor, or service) is designed to operate or provide coverage.
  • B. coverageScope chosen
    Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
  • C. scopeCharacterization
    Indicates how the extent, boundaries, or coverage of something is defined, described, or qualified in relation to another entity or context.
  • D. keyCoverage
    Indicates that one entity provides coverage, protection, or applicability for another in a way that is essential or central to its function or requirements.
  • E. runtimeCharacteristic
    Indicates a relationship where a system, process, or component is associated with a property or behavior that specifically manifests during its execution or operation time.
  • 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_69aed932cab48190b80ffe35f7029ae1 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02c87cc88190a9ec3712db18a8a7 completed March 9, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69af018fb0948190a9701b2e8e5d9bac completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:45 p.m.