Triple
T28400338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synchronous Digital Hierarchy |
E719378
|
entity |
| Predicate | usesMultiplexingStructure |
P51279
|
FINISHED |
| Object | Virtual Container |
—
|
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: Virtual Container | Statement: [Synchronous Digital Hierarchy, usesMultiplexingStructure, Virtual Container]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultiplexingStructure Context triple: [Synchronous Digital Hierarchy, usesMultiplexingStructure, Virtual Container]
-
A.
multiplexType
Indicates the specific kind or category of multiplex relationship or connection that exists between entities.
-
B.
multiplexing
chosen
Indicates combining multiple signals or data streams into a single channel or medium for transmission or processing.
-
C.
supportsLayeredDivisionMultiplexing
Indicates that one entity enables or is compatible with the use of layered division multiplexing techniques in conjunction with another entity.
-
D.
usesDuplexMethod
Indicates that one entity employs a duplex method, meaning a two-way or bidirectional technique or process, in relation to another entity or context.
-
E.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 1:19 a.m.