Triple

T34170213
Position Surface form Disambiguated ID Type / Status
Subject Gymnarchus E876522 entity
Predicate electrocommunication P198862 FINISHED
Object true 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: true | Statement: [Gymnarchus, electrocommunication, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electrocommunication
Context triple: [Gymnarchus, electrocommunication, true]
  • A. telecommunication
    Indicates the establishment or use of long-distance electronic communication between entities, such as transmitting information via phone, radio, or digital networks.
  • B. usesTelecommunications
    Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
  • C. designedToCommunicate
    Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
  • D. usedToCommunicate
    Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
  • E. telecommunicationSystem
    Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
  • 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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff0e9c75208190a4423261f00b79b3 completed May 9, 2026, 10:38 a.m.
PD Predicate disambiguation batch_69ff0e07f08481909c4ae322632a6bf0 completed May 9, 2026, 10:35 a.m.
PDg Predicate description generation batch_69ff0e9b7acc81909a0ee66201a06877 completed May 9, 2026, 10:38 a.m.
Created at: May 1, 2026, 1:54 a.m.