Triple
T9030104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modbus RTU |
E216146
|
entity |
| Predicate | usesErrorChecking |
P5658
|
FINISHED |
| Object | CRC |
—
|
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: CRC | Statement: [Modbus RTU, usesErrorChecking, CRC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesErrorChecking Context triple: [Modbus RTU, usesErrorChecking, CRC]
-
A.
usesIntegrityCheck
chosen
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
B.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
-
C.
usesForwardErrorCorrection
Indicates that one entity applies forward error correction techniques to detect and correct errors in data transmitted to or received from another entity.
-
D.
usedExperimentalMethod
Indicates that an entity employed a specific experimental method or technique in carrying out an action, study, or investigation.
-
E.
usesPMD
Indicates that one entity employs or applies PMD (a specific tool, method, or metric) in relation to another entity or context.
- F. None of above.
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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.