Triple
T4260556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100BASE-T4 |
E96091
|
entity |
| Predicate | OSIPhysicalLayer |
P1377
|
FINISHED |
| Object | Layer 1 |
—
|
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: Layer 1 | Statement: [100BASE-T4, OSIPhysicalLayer, Layer 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIPhysicalLayer Context triple: [100BASE-T4, OSIPhysicalLayer, Layer 1]
-
A.
physicalLayer
chosen
Indicates a relationship where one entity functions as or pertains to the lowest (physical) layer in a layered system or communication stack, handling the actual transmission of signals or raw data.
-
B.
usesPhysicalLayerPipe
Indicates that one entity employs a specific physical-layer transmission path or channel provided by another entity to carry its data.
-
C.
usesPhysicalLayerSimilarTo
Indicates that one entity employs a physical layer that is similar in structure, technology, or operational characteristics to that used by another entity.
-
D.
physicalLayerDesignation
Indicates that one entity specifies or assigns the physical-layer characteristics or identifier used by another entity in a communication system.
-
E.
protocolLayer
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.