Triple
T5782324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Flats Plant |
E128187
|
entity |
| Predicate | addedToSuperfund |
P65811
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Rocky Flats Plant, addedToSuperfund, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToSuperfund Context triple: [Rocky Flats Plant, addedToSuperfund, 1989]
-
A.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
C.
addedToNRHP
Indicates that something has been officially listed on the National Register of Historic Places.
-
D.
landfilledFrom
Indicates that material, waste, or items originate from a specified source and are disposed of by being placed into a landfill at the target location.
-
E.
environmentalRemediation
Indicates actions or processes undertaken to remove, reduce, or neutralize pollution or environmental damage in order to restore a site or ecosystem to a safer or more natural condition.
- F. None of above. chosen
Provenance (4 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a17315881908aa12a830ba5f22b |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:50 p.m.