Triple
T20657941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3by |
E507675
|
entity |
| Predicate | definesConnectorUsage |
P37271
|
FINISHED |
| Object | SFP28 form factor 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: SFP28 form factor modules | Statement: [IEEE 802.3by, definesConnectorUsage, SFP28 form factor modules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesConnectorUsage Context triple: [IEEE 802.3by, definesConnectorUsage, SFP28 form factor modules]
-
A.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
B.
definesConnectorColor
Indicates that an entity specifies or assigns the color of a connector.
-
C.
usesTConnectorsAtStations
Indicates that the subject employs T-shaped connectors at stations as part of its configuration or infrastructure.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
definesUseOf
chosen
Indicates that one entity specifies or determines how another entity is to be used or applied.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.