Triple
T20337170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-R PCS |
E495643
|
entity |
| Predicate | scramblerType |
P41109
|
FINISHED |
| Object | self-synchronous scrambler |
—
|
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: self-synchronous scrambler | Statement: [10GBASE-R PCS, scramblerType, self-synchronous scrambler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scramblerType Context triple: [10GBASE-R PCS, scramblerType, self-synchronous scrambler]
-
A.
usesScrambling
chosen
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
B.
requiresScramble
Indicates that one entity must be mixed, randomized, or rearranged (scrambled) as a necessary condition for another entity, action, or process to occur or be valid.
-
C.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
D.
ciphertextType
Indicates the specific kind or format of ciphertext produced or used in an encryption process.
-
E.
spinType
Indicates the specific kind or category of spin associated with an entity, such as its spin state, mode, or configuration.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677ed75e081909bfc534033ac1c59 |
completed | April 20, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.