Triple
T6978712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onondaga Lake |
E161780
|
entity |
| Predicate | cleanupMethod |
P73620
|
FINISHED |
| Object | dredging of contaminated sediments |
—
|
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: dredging of contaminated sediments | Statement: [Onondaga Lake, cleanupMethod, dredging of contaminated sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleanupMethod Context triple: [Onondaga Lake, cleanupMethod, dredging of contaminated sediments]
-
A.
cleanupProgram
Indicates that an entity is involved in or responsible for a program or initiative focused on cleaning up or removing waste, pollution, or unwanted materials.
-
B.
cleanupDrivenBy
Indicates that a cleanup activity is initiated, motivated, or caused by a specified agent, factor, or process.
-
C.
cleanupManagedBy
Indicates that the cleanup or removal of something is handled or controlled by a specified managing entity.
-
D.
functionBeforeDestruction
Indicates that one function or operation occurs prior in time to a specified destruction event.
-
E.
afterDestruction
Indicates that one event, state, or condition occurs subsequent to and as a result of a prior act of destruction.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6aa6188190af7656ff4d0e3230 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8e2d7b48190b37bb13984663cde |
completed | March 27, 2026, 7:22 p.m. |
Created at: March 27, 2026, 2:31 p.m.