Triple

T2575211
Position Surface form Disambiguated ID Type / Status
Subject Consumer Confidence Reports E57758 entity
Predicate supportGoal P39887 FINISHED
Object public right-to-know about drinking water quality 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 right-to-know about drinking water quality | Statement: [Consumer Confidence Reports, supportGoal, public right-to-know about drinking water quality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportGoal
Context triple: [Consumer Confidence Reports, supportGoal, public right-to-know about drinking water quality]
  • A. support
    Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
  • B. legacyGoal
    Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
  • C. goals
    Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
  • D. statedAsGoalFor
    Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
  • E. secondaryGoal
    Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69abd251b48c8190862c7b39ea1bf8ea completed March 7, 2026, 7:22 a.m.
Created at: March 6, 2026, 9:48 p.m.