Triple
T21257908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richland-Chambers Reservoir |
E523916
|
entity |
| Predicate | yearImpounded |
P27957
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Richland-Chambers Reservoir, yearImpounded, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearImpounded Context triple: [Richland-Chambers Reservoir, yearImpounded, 1987]
-
A.
impoundmentYear
chosen
Indicates the year in which something (typically property, funds, or resources) was officially impounded or taken into custody by an authority.
-
B.
arrestYear
Indicates the calendar year in which an arrest took place.
-
C.
impoundedBy
Indicates that an authority or agent has seized and taken legal custody of an entity, typically restricting its use or movement.
-
D.
impounds
Indicates the act of seizing and holding property, typically by an authority, so it is kept in custody and temporarily removed from the owner’s control.
-
E.
suspensionYear
Indicates the year in which a suspension (such as a ban, halt, or temporary discontinuation of activity) takes effect or is recorded.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e2f1d48190b566ab4d736fdbc4 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:58 p.m.