Triple
T18227512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Baby |
E436456
|
entity |
| Predicate | powerConsumptionWatts |
P130319
|
FINISHED |
| Object | 3500 |
—
|
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: 3500 | Statement: [Manchester Baby, powerConsumptionWatts, 3500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerConsumptionWatts Context triple: [Manchester Baby, powerConsumptionWatts, 3500]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
powerAdapterWattage
Indicates the electrical power capacity, in watts, that a power adapter can supply.
-
C.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
D.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b0ed5c819096f4fd3a8debc1a4 |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.