Triple
T20638684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 200GBASE-R PHYs |
E507157
|
entity |
| Predicate | supportsClockRecovery |
P127629
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [200GBASE-R PHYs, supportsClockRecovery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClockRecovery Context triple: [200GBASE-R PHYs, supportsClockRecovery, yes]
-
A.
clockRecovery
chosen
Indicates the process or relationship by which a receiver reconstructs or synchronizes its clock signal from an incoming data stream or signal.
-
B.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
C.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
D.
usesForwardErrorCorrection
Indicates that one entity applies forward error correction techniques to detect and correct errors in data transmitted to or received from another entity.
-
E.
designedToRecover
Indicates that something is intentionally created or configured for the purpose of regaining a prior state, condition, or resource after loss, damage, or failure.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad1163008190aa9df36750a952d2 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.