Triple
T26580479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Water Quality Act of 1987 |
E667063
|
entity |
| Predicate | section402pSubject |
P450
|
FINISHED |
| Object | stormwater discharge permitting |
—
|
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: stormwater discharge permitting | Statement: [Water Quality Act of 1987, section402pSubject, stormwater discharge permitting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: section402pSubject Context triple: [Water Quality Act of 1987, section402pSubject, stormwater discharge permitting]
-
A.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
fourthPartSubject
Indicates that the subject is the fourth part or component within a larger ordered whole or sequence.
-
C.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
D.
secondPartSubject
Indicates that the referenced entity serves as the second part or component of the subject in a composite or multipart relationship.
-
E.
annexBSubject
Indicates that one entity is the subject or main focus of Annex B in relation to 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_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_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:02 a.m.