Triple
T10474931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxor Sky Beam |
E247018
|
entity |
| Predicate | totalPowerConsumption |
P34611
|
FINISHED |
| Object | approximately 315,000 watts |
—
|
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: approximately 315,000 watts | Statement: [Luxor Sky Beam, totalPowerConsumption, approximately 315,000 watts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalPowerConsumption Context triple: [Luxor Sky Beam, totalPowerConsumption, approximately 315,000 watts]
-
A.
electricityUse
chosen
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
B.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
C.
airPowerUsedBy
Indicates that a particular actor employs or deploys air power (such as aircraft or aerial operations) as part of its activities or capabilities.
-
D.
showsPowerUse
Indicates that one entity demonstrates or exercises power, influence, or control over another entity or within a given context.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094f6b408190a5a26b1a82e4a02b |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.