Triple
T38541087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EtherNet/IP |
E924835
|
entity |
| Predicate | transportLayerProtocols |
P10376
|
FINISHED |
| Object | TCP |
—
|
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: TCP | Statement: [EtherNet/IP, transportLayerProtocols, TCP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportLayerProtocols Context triple: [EtherNet/IP, transportLayerProtocols, TCP]
-
A.
transportProtocol
chosen
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
tunnelsProtocol
Indicates that one communication protocol is encapsulated and transmitted within another protocol, creating a tunnel through the outer protocol’s channel.
-
C.
networkLayerSupport
Indicates that one entity provides or is compatible with the network-layer functionality or protocols required by another entity.
-
D.
transportLayerFor
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
E.
applicationLayerProtocol
Indicates that one entity uses, implements, or is associated with a specific application-layer communication protocol in a networked interaction.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: May 3, 2026, 4:32 p.m.