Triple
T36883597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequoia |
E911546
|
entity |
| Predicate | powerUsageMW |
P178611
|
FINISHED |
| Object | on the order of 6 |
—
|
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: on the order of 6 | Statement: [Sequoia, powerUsageMW, on the order of 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerUsageMW Context triple: [Sequoia, powerUsageMW, on the order of 6]
-
A.
electricPowerOutput
Indicates the amount of electrical power produced or delivered by an entity.
-
B.
powerUse
chosen
Indicates the amount or manner in which one entity consumes or utilizes power or energy in relation to another entity or context.
-
C.
netElectricalCapacity_MWe
Indicates the relationship specifying an entity’s net electrical power generation capacity, measured in megawatts electric (MWe), after accounting for internal power consumption.
-
D.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
E.
powerConsumptionWatts
Indicates the amount of electrical power an entity uses, measured in watts, during its operation.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:13 p.m.