Triple
T7154597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enedis |
E166777
|
entity |
| Predicate | gridTypeManaged |
P51437
|
FINISHED |
| Object | medium-voltage distribution grid |
—
|
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: medium-voltage distribution grid | Statement: [Enedis, gridTypeManaged, medium-voltage distribution grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridTypeManaged Context triple: [Enedis, gridTypeManaged, medium-voltage distribution grid]
-
A.
gridType
Indicates the specific structural or organizational pattern of a grid used to arrange or reference elements.
-
B.
gridSize
Indicates the dimensions or scale of a grid used to structure or partition a space or dataset.
-
C.
gridRegion
Indicates a spatial relationship where an entity is located within, or associated with, a specific region or cell of a grid.
-
D.
regulatesGridThrough
Indicates that one entity controls or influences the operation or behavior of an electrical grid by means of another specified intermediary or mechanism.
-
E.
typeOfPropertyManaged
chosen
Indicates the specific category or kind of property that an entity is responsible for managing.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80c747c8190a017a2b1c3e78a3f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.