Triple
T35627675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANopen |
E1029498
|
entity |
| Predicate | hasCommunicationObject |
P207069
|
FINISHED |
| Object | Process Data Object |
—
|
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: Process Data Object | Statement: [CANopen, hasCommunicationObject, Process Data Object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunicationObject Context triple: [CANopen, hasCommunicationObject, Process Data Object]
-
A.
hasCommunicationAccess
Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
-
B.
hasCommunicationClass
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
C.
hasCommunicationType
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
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.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.