Triple
T26580478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Water Quality Act of 1987 |
E667063
|
entity |
| Predicate | addsSection |
P25351
|
FINISHED |
| Object | Section 402(p) of the Clean Water Act |
—
|
NE NERFINISHED |
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: Section 402(p) of the Clean Water Act | Statement: [Water Quality Act of 1987, addsSection, Section 402(p) of the Clean Water Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsSection Context triple: [Water Quality Act of 1987, addsSection, Section 402(p) of the Clean Water Act]
-
A.
extendedSection
Indicates that one section is a continuation or elaborated extension of another section.
-
B.
sectionCreated
chosen
Indicates that a new section has been created or added within a larger structure, document, or system.
-
C.
supportsSection
Indicates that one entity provides structural or functional backing or reinforcement to a specific section of another entity.
-
D.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
E.
sectionCreates
Indicates that a particular section is responsible for creating or generating another entity, resource, or content.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e0f3688190a10114486c5d62ab |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:02 a.m.