Triple
T18107641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blenheim-Gilboa Pumped Storage Power Project |
E433384
|
entity |
| Predicate | gridService |
P130476
|
FINISHED |
| Object | frequency regulation |
—
|
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: frequency regulation | Statement: [Blenheim-Gilboa Pumped Storage Power Project, gridService, frequency regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridService Context triple: [Blenheim-Gilboa Pumped Storage Power Project, gridService, frequency regulation]
-
A.
gridName
Indicates the name or identifier assigned to a particular grid within a system or dataset.
-
B.
gridRegion
Indicates a spatial relationship where an entity is located within, or associated with, a specific region or cell of a grid.
-
C.
gridType
Indicates the specific structural or organizational pattern of a grid used to arrange or reference elements.
-
D.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
E.
gridSize
Indicates the dimensions or scale of a grid used to structure or partition a space or dataset.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.