Triple
T501570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3at |
E10412
|
entity |
| Predicate | maximumPSEOutputPowerPerPort |
P4633
|
FINISHED |
| Object | 30 W |
—
|
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: 30 W | Statement: [IEEE 802.3at, maximumPSEOutputPowerPerPort, 30 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPSEOutputPowerPerPort Context triple: [IEEE 802.3at, maximumPSEOutputPowerPerPort, 30 W]
-
A.
maximumPowerAtPSE
chosen
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
B.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
C.
maxPowerDelivery
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
D.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
E.
maximumDevicesPerBus
Indicates the maximum number of devices that are allowed to be connected to a single bus.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f131e2148190afd43402f505c73e |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.