Triple

T21714458
Position Surface form Disambiguated ID Type / Status
Subject Summit Airport E535986 entity
Predicate has communication type P112150 FINISHED
Object common traffic advisory frequency 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: common traffic advisory frequency | Statement: [Summit Airport, has communication type, common traffic advisory frequency]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: has communication type
Context triple: [Summit Airport, has communication type, common traffic advisory frequency]
  • A. hasCommunicationType chosen
    Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
  • B. hasCommunicationClass
    Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
  • C. hasCommunicationCodeType
    Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
  • D. hasCommunicationInterface
    Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
  • E. hasCommunicationDomain
    Indicates that one entity operates, functions, or is relevant within a specified communication-related domain or area.
  • 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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efb5369be88190bafc10863d4d1bd7 completed April 27, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69e6969725bc81908e7ad19619ba2688 completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:47 p.m.