Triple

T21947334
Position Surface form Disambiguated ID Type / Status
Subject Merkur Mountain E541966 entity
Predicate hasCommunicationUse P146649 FINISHED
Object site for transmission installations 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: site for transmission installations | Statement: [Merkur Mountain, hasCommunicationUse, site for transmission installations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunicationUse
Context triple: [Merkur Mountain, hasCommunicationUse, site for transmission installations]
  • A. usedToCommunicate
    Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
  • B. hasCommunicationType
    Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
  • C. usesTelecommunications
    Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
  • D. hasCommunicationFrequency
    Indicates how often communication occurs between the related entities.
  • E. hasCommunicationLimitation
    Indicates that an entity is subject to some restriction, constraint, or reduced capacity in its ability to communicate.
  • 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_69e0c47ef0e48190a50e1bcc43f4b3fd completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12428dee48190acb63051ed7cd03e completed April 28, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69e6f5efc208819091ed2cf6841fa600 completed April 21, 2026, 3:58 a.m.
PDg Predicate description generation batch_69e6fb6991948190a428c3c3bfd1c3b8 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 7:57 p.m.