Triple
T9029801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.fast |
E216138
|
entity |
| Predicate | powerFeedingOption |
P85773
|
FINISHED |
| Object | reverse power feeding from customer premises equipment |
—
|
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: reverse power feeding from customer premises equipment | Statement: [G.fast, powerFeedingOption, reverse power feeding from customer premises equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerFeedingOption Context triple: [G.fast, powerFeedingOption, reverse power feeding from customer premises equipment]
-
A.
powerFeeding
Indicates a relationship where one entity supplies electrical power to another entity for its operation or charging.
-
B.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
-
C.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
D.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
E.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.