Triple
T5934177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veolia Environnement |
E132003
|
entity |
| Predicate | regulatorySector |
P54742
|
FINISHED |
| Object | public utilities |
—
|
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: public utilities | Statement: [Veolia Environnement, regulatorySector, public utilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorySector Context triple: [Veolia Environnement, regulatorySector, public utilities]
-
A.
industryRegime
Indicates a regulatory or governance framework that controls or shapes how an industry operates.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
governmentTypeRegulated
Indicates that the type or form of government of an entity is subject to regulation, control, or definition by another authority or governing framework.
-
D.
regulatoryField
chosen
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
-
E.
notableSector
Indicates that an entity is particularly prominent, influential, or significant within a specified sector or industry.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.