Triple

T38059668
Position Surface form Disambiguated ID Type / Status
Subject Scottish UIR E950304 entity
Predicate radioCommunicationRequired P189977 FINISHED
Object yes 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: yes | Statement: [Scottish UIR, radioCommunicationRequired, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: radioCommunicationRequired
Context triple: [Scottish UIR, radioCommunicationRequired, yes]
  • A. radioOperator
    Indicates a relationship where one entity serves as the radio operator for another, handling radio communication duties on its behalf.
  • B. radioSystem
    Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
  • C. radioDistressChannel
    Indicates that an entity is using or associated with a radio channel designated specifically for transmitting distress or emergency communications.
  • D. enablesCommunicationWith
    Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
  • E. radioInterface
    Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
  • F. None of above. chosen

Provenance (4 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_69f76f01e63c819093b6012fc974f35a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc4748843c8190931432653be4890c completed May 7, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69fc45646ce481908caf292ff9f06e15 completed May 7, 2026, 7:55 a.m.
PDg Predicate description generation batch_69fc4747b06c8190a3ea5331f02eedad completed May 7, 2026, 8:03 a.m.
Created at: May 3, 2026, 4:21 p.m.