Triple
T767850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power over Ethernet |
E16214
|
entity |
| Predicate | transportsPowerAndDataOver |
P11429
|
FINISHED |
| Object | single Ethernet cable |
—
|
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: single Ethernet cable | Statement: [Power over Ethernet, transportsPowerAndDataOver, single Ethernet cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportsPowerAndDataOver Context triple: [Power over Ethernet, transportsPowerAndDataOver, single Ethernet cable]
-
A.
maxPowerDelivery
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
B.
supportsPowerDelivery
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
isTypicallyWiredUsing
chosen
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
E.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.