Triple
T9107030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEOM |
E218502
|
entity |
| Predicate | energyStrategy |
P86516
|
FINISHED |
| Object | 100% renewable energy |
—
|
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: 100% renewable energy | Statement: [NEOM, energyStrategy, 100% renewable energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyStrategy Context triple: [NEOM, energyStrategy, 100% renewable energy]
-
A.
energyAspect
Indicates a relationship where one entity represents an aspect, component, or characteristic related to the energy properties or behavior of another entity.
-
B.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
C.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
D.
energyContext
Indicates the situational or environmental conditions under which energy is produced, used, transferred, or transformed in relation to the entities involved.
-
E.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca573da0081909f4afcdb3ac99c53 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.