Triple

T22496512
Position Surface form Disambiguated ID Type / Status
Subject Rhodes Point E556153 entity
Predicate hasCommunicationAccess P148437 FINISHED
Object limited on-island services 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: limited on-island services | Statement: [Rhodes Point, hasCommunicationAccess, limited on-island services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunicationAccess
Context triple: [Rhodes Point, hasCommunicationAccess, limited on-island services]
  • A. hasCommunicationUse
    Indicates that something is used for, or serves the purpose of, communication.
  • B. hasCommunicationType
    Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
  • C. 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.
  • D. enablesCommunicationWith
    Indicates that one entity provides the means or capability for another entity to communicate with a specified party 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. 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_69e11e5445bc8190b6a9481926db3355 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15cb2644c819094864bd88bcebcbd completed April 29, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69e898be31448190be5ae7f5656f0497 completed April 22, 2026, 9:45 a.m.
PDg Predicate description generation batch_69e8aa3b4c288190951cca06d42bea51 completed April 22, 2026, 11 a.m.
Created at: April 16, 2026, 8:50 p.m.