Triple
T21267915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GWA |
E524176
|
entity |
| Predicate | publicUtilityStatus |
P90435
|
FINISHED |
| Object | regulated public utility |
—
|
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: regulated public utility | Statement: [GWA, publicUtilityStatus, regulated public utility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicUtilityStatus Context triple: [GWA, publicUtilityStatus, regulated public utility]
-
A.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
publicUtility
chosen
Indicates that an entity provides essential services or infrastructure for the general public’s use and benefit, typically under public regulation or oversight.
-
D.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
E.
usageStatus
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735ee38cc81909b4e7c5996bb64f9 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4 p.m.