Triple
T24274515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XEL |
E605369
|
entity |
| Predicate | issuerRegulatedBy |
P68074
|
FINISHED |
| Object | state public utility commissions |
—
|
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: state public utility commissions | Statement: [XEL, issuerRegulatedBy, state public utility commissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerRegulatedBy Context triple: [XEL, issuerRegulatedBy, state public utility commissions]
-
A.
issuerRegulatoryFilingAuthority
Indicates the regulatory body or authority with which an issuer files its official regulatory or disclosure documents.
-
B.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
C.
typeOfAgencyRegulated
Indicates that one entity is the kind or category of agency that is subject to regulation by another entity.
-
D.
formerlyRegulatedBy
Indicates that an entity was previously subject to the authority or control of a particular regulator, but is no longer regulated by that entity.
-
E.
hasRegulatedBy
chosen
Indicates that one entity is subject to control, governance, or rules imposed 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.