Triple

T594728
Position Surface form Disambiguated ID Type / Status
Subject Corvallis Municipal Airport E17353 entity
Predicate hasCommunicationFrequency P15845 FINISHED
Object CTAF/UNICOM 122.8 MHz 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: CTAF/UNICOM 122.8 MHz | Statement: [Corvallis Municipal Airport, hasCommunicationFrequency, CTAF/UNICOM 122.8 MHz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunicationFrequency
Context triple: [Corvallis Municipal Airport, hasCommunicationFrequency, CTAF/UNICOM 122.8 MHz]
  • A. meetingFrequency
    Indicates how often a meeting or recurring gathering takes place over a given period.
  • B. communicationMode
    Indicates the method or channel through which communication between entities is carried out.
  • C. hasInteraction
    Indicates that there is some form of interaction or mutual action occurring between the related entities.
  • D. hasTeleconnectionsWith
    Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
  • E. communicationChannel
    Indicates a medium or method through which information is transmitted between parties.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bd280ac8190b6a530ce73da85c8 completed March 1, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69a494ceeb7881909a91ed1a35d5bf0a completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a4985b7d7481909b5d30f4001ed61c completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:33 p.m.