Triple
T4384906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PROFINET IRT |
E99217
|
entity |
| Predicate | comparedTo |
P278
|
FINISHED |
| Object | PROFINET RT |
E437258
|
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: PROFINET RT | Statement: [PROFINET IRT, comparedTo, PROFINET RT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PROFINET RT Context triple: [PROFINET IRT, comparedTo, PROFINET RT]
-
A.
PROFINET RT
chosen
PROFINET RT is a real-time industrial Ethernet communication protocol widely used for time-critical data exchange in automation systems.
-
B.
PROFINET IRT
PROFINET IRT is a real-time industrial Ethernet communication technology designed for high-speed, deterministic data exchange in automation and motion control applications.
-
C.
PROFIBUS and PROFINET International
PROFIBUS and PROFINET International is a global industrial automation organization that develops, standardizes, and promotes the PROFIBUS and PROFINET communication technologies used in factory and process automation.
-
D.
EtherCAT
EtherCAT is a high-performance industrial Ethernet protocol designed for real-time control in automation systems.
-
E.
Sercos III
Sercos III is a real-time industrial Ethernet communication standard widely used for high-performance motion control and automation systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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. |
| NED1 | Entity disambiguation (via context triple) | batch_69b6135919d08190abab3858ff01bf11 |
completed | March 15, 2026, 2:03 a.m. |
Created at: March 12, 2026, 11:19 p.m.