Triple
T31522955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaybah residential and industrial complex |
E804255
|
entity |
| Predicate | energySupply |
P118200
|
FINISHED |
| Object | on-site power generation |
—
|
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-site power generation | Statement: [Shaybah residential and industrial complex, energySupply, on-site power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySupply Context triple: [Shaybah residential and industrial complex, energySupply, on-site power generation]
-
A.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
B.
energyHub
chosen
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
-
C.
energyName
Indicates that a specific name or label is assigned to an energy-related quantity, type, or resource.
-
D.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
-
E.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 30, 2026, 9:57 p.m.