Triple
T637961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-T |
E16665
|
entity |
| Predicate | supportsMDI_MDIX |
P18341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [10GBASE-T, supportsMDI_MDIX, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMDI_MDIX Context triple: [10GBASE-T, supportsMDI_MDIX, true]
-
A.
supportsDisplayPortAltMode
Indicates that one entity is capable of transmitting video and audio using the DisplayPort Alternate Mode over a USB-C or similar connection to another entity.
-
B.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
supportsMultipleDataAndDisplayProtocols
Indicates that an entity is capable of handling more than one type of data protocol and more than one type of display protocol.
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a4a1794a60819092b3dc3344426ed7 |
completed | March 1, 2026, 8:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.