Triple
T26379104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samsung Adaptive Fast Charging |
E660974
|
entity |
| Predicate | typicalMaxPower |
P89369
|
FINISHED |
| Object | 15W |
—
|
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: 15W | Statement: [Samsung Adaptive Fast Charging, typicalMaxPower, 15W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaxPower Context triple: [Samsung Adaptive Fast Charging, typicalMaxPower, 15W]
-
A.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
B.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
-
C.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
D.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
E.
optionalPowerOutput
Indicates that an entity may have a specified power output value, but this value is not required to be present.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 26, 2026, 11:03 p.m.