Triple
T16747092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | demultiplexes |
P1175
|
FINISHED |
| Object | incoming frames to appropriate higher-layer handler |
—
|
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: incoming frames to appropriate higher-layer handler | Statement: [DSAP, demultiplexes, incoming frames to appropriate higher-layer handler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demultiplexes Context triple: [DSAP, demultiplexes, incoming frames to appropriate higher-layer handler]
-
A.
demodulatedBy
Indicates that a modulated signal has been processed to extract its original baseband information by a specified demodulation method or device.
-
B.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
deconstructs
Indicates that one entity systematically takes apart, analyzes, or dismantles another entity or its structure into constituent elements.
-
D.
multiplexing
Indicates combining multiple signals or data streams into a single channel or medium for transmission or processing.
-
E.
demotes
Indicates that one entity reduces another entity’s rank, status, or level within a hierarchy or system.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.