Triple
T1445054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 92-500 |
E31157
|
entity |
| Predicate | goalYear |
P26643
|
FINISHED |
| Object | 1983 fishable and swimmable waters goal |
—
|
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: 1983 fishable and swimmable waters goal | Statement: [Public Law 92-500, goalYear, 1983 fishable and swimmable waters goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalYear Context triple: [Public Law 92-500, goalYear, 1983 fishable and swimmable waters goal]
-
A.
hasGoalYear
chosen
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
B.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
C.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
D.
year
Indicates the specific calendar year associated with an entity, event, or fact.
-
E.
banYear
Indicates the year in which a ban was enacted or came into effect on the related entity or activity.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.