Triple
T767877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power over Ethernet |
E16214
|
entity |
| Predicate | usesPowerPairs |
P14386
|
FINISHED |
| Object | spare pairs in 10/100BASE-T |
—
|
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: spare pairs in 10/100BASE-T | Statement: [Power over Ethernet, usesPowerPairs, spare pairs in 10/100BASE-T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowerPairs Context triple: [Power over Ethernet, usesPowerPairs, spare pairs in 10/100BASE-T]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
C.
powerBy
chosen
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
-
E.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, 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_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.