Triple
T35627723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANopen |
E1029498
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object |
CANopen Safety
CANopen Safety is a safety-oriented extension of the CANopen communication protocol designed to meet functional safety requirements in industrial and automation systems.
|
E1029498
|
NE 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: CANopen Safety | Statement: [CANopen, hasVariant, CANopen Safety]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: CANopen Safety Triple: [CANopen, hasVariant, CANopen Safety]
Generated description
CANopen Safety is a safety-oriented extension of the CANopen communication protocol designed to meet functional safety requirements in industrial and automation systems.
Provenance (5 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_69f79f15e6ac8190916822e28724534a |
completed | May 3, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387277ca7481909296dfe402c5471a |
completed | June 21, 2026, 11:23 p.m. |
| NEDg | Description generation | batch_6a3872f184f88190ad26c3ef815b21c6 |
completed | June 21, 2026, 11:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a387337fa9c8190833f60c3a5bbb20a |
completed | June 21, 2026, 11:26 p.m. |
Created at: May 3, 2026, 4:05 p.m.