Triple
T31008528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elwha Dam |
E790140
|
entity |
| Predicate | removedAsPartOf |
P124287
|
FINISHED |
| Object | Elwha River Restoration Project |
—
|
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: Elwha River Restoration Project | Statement: [Elwha Dam, removedAsPartOf, Elwha River Restoration Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedAsPartOf Context triple: [Elwha Dam, removedAsPartOf, Elwha River Restoration Project]
-
A.
removedAs
Indicates that one entity has been taken out of a position, role, or context in relation to another entity.
-
B.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
C.
removalPartOf
chosen
Indicates that one entity is a component or portion that has been taken away or extracted from another entity.
-
D.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
E.
removedUnder
Indicates that one entity was taken away, eliminated, or withdrawn while being subject to the authority, control, or conditions imposed by 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 8:57 p.m.