Triple

T4384890
Position Surface form Disambiguated ID Type / Status
Subject PROFINET IRT E99217 entity
Predicate hasCommunicationClass P56285 FINISHED
Object Class C 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: Class C | Statement: [PROFINET IRT, hasCommunicationClass, Class C]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunicationClass
Context triple: [PROFINET IRT, hasCommunicationClass, Class C]
  • A. 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.
  • B. hasCommunicationCodeType
    Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
  • C. hasCommunicationDomain
    Indicates that one entity operates, functions, or is relevant within a specified communication-related domain or area.
  • D. hasCommunicationIdentifier
    Indicates that an entity is associated with a specific communication-related identifier (such as a phone number, email address, or messaging handle) used for contact or messaging purposes.
  • E. hasCommunicationFrequency
    Indicates how often communication occurs between the related entities.
  • 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_69b3454f739481909ff6c28331f0c0b9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35264e44c81908dd0e0a81f1353bb completed March 12, 2026, 11:55 p.m.
PD Predicate disambiguation batch_69b34f572efc8190bad1e5078cbcb75a completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b3501834448190bedf775a80da4778 completed March 12, 2026, 11:45 p.m.
Created at: March 12, 2026, 11:19 p.m.