Triple
T241002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clean Water Act |
E4930
|
entity |
| Predicate | amendedIn |
P5571
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Clean Water Act, amendedIn, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amendedIn Context triple: [Clean Water Act, amendedIn, 1977]
-
A.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
B.
hasAmendments
chosen
Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
-
C.
amendmentCount
Indicates the number of amendments that have been made to a given item, document, or entity.
-
D.
amendmentRequires
Indicates that a particular amendment is necessary or must be applied in relation to another item, document, or condition.
-
E.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b60ad308190b12f119960a8bde7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.