Triple
T20337183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-R PCS |
E495643
|
entity |
| Predicate | usesControlBlocks |
P139743
|
FINISHED |
| Object | special 66b control block types |
—
|
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: special 66b control block types | Statement: [10GBASE-R PCS, usesControlBlocks, special 66b control block types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlBlocks Context triple: [10GBASE-R PCS, usesControlBlocks, special 66b control block types]
-
A.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
B.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
C.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
D.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:23 a.m.