Triple
T501587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3at |
E10412
|
entity |
| Predicate | powerDeliveryMethod |
P1486
|
FINISHED |
| Object | phantom power over data pairs |
—
|
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: phantom power over data pairs | Statement: [IEEE 802.3at, powerDeliveryMethod, phantom power over data pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDeliveryMethod Context triple: [IEEE 802.3at, powerDeliveryMethod, phantom power over data pairs]
-
A.
supportsPowerDelivery
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
-
B.
maxPowerDelivery
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
C.
disbursementOption
Indicates the method or arrangement by which funds are paid out or distributed.
-
D.
deliveryMode
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
E.
distributionMethod
chosen
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
- 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.