Triple
T18946201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3bt |
E463519
|
entity |
| Predicate | maximumPSEPower |
P4633
|
FINISHED |
| Object | 60 W for Type 3 |
—
|
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: 60 W for Type 3 | Statement: [IEEE 802.3bt, maximumPSEPower, 60 W for Type 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPSEPower Context triple: [IEEE 802.3bt, maximumPSEPower, 60 W for Type 3]
-
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.
maximumEnergy
Indicates the greatest amount of energy that an entity can possess, store, or output under specified conditions.
-
C.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
-
D.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
E.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d53f6eb8819099b1268db8b14d66 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.