Triple
T2575216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consumer Confidence Reports |
E57758
|
entity |
| Predicate | oftenMadeAvailableVia |
P36522
|
FINISHED |
| Object | water system websites |
—
|
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: water system websites | Statement: [Consumer Confidence Reports, oftenMadeAvailableVia, water system websites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenMadeAvailableVia Context triple: [Consumer Confidence Reports, oftenMadeAvailableVia, water system websites]
-
A.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
B.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
C.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
D.
availableOnlineAt
chosen
Indicates that something can be accessed or obtained via a specified online source or location.
-
E.
availability
Indicates that an entity is present, accessible, or ready for use or interaction 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a43f188190a3d7538bf7867466 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.