Triple
T20638667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 200GBASE-R PHYs |
E507157
|
entity |
| Predicate | supportsFormFactors |
P83353
|
FINISHED |
| Object | QSFP56 modules |
—
|
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: QSFP56 modules | Statement: [200GBASE-R PHYs, supportsFormFactors, QSFP56 modules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFormFactors Context triple: [200GBASE-R PHYs, supportsFormFactors, QSFP56 modules]
-
A.
supportsDriveFormFactor
Indicates that one entity is compatible with or can accommodate a specified physical form factor of a drive.
-
B.
supportsFormFactorFamily
chosen
Indicates that one entity is compatible with and can operate using a specified family of physical or design form factors.
-
C.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
D.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with another entity.
-
E.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
- 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.