Triple
T26517821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayou Bonfouca |
E669866
|
entity |
| Predicate | cleanupActions |
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: [Bayou Bonfouca, cleanupActions, dredging of contaminated sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleanupActions Context triple: [Bayou Bonfouca, cleanupActions, dredging of contaminated sediments]
-
A.
cleanupOperation
Indicates an action where an entity removes, resets, or tidies up residual data, resources, or state after a process or event has completed.
-
B.
cleanupMethod
chosen
Indicates the method or procedure used to clean up, remove, or reset something after an operation or event.
-
C.
cleanupOutcome
Indicates the result or status produced by a cleanup action or process.
-
D.
cleanupDrivenBy
Indicates that a cleanup activity is initiated, motivated, or caused by a specified agent, factor, or process.
-
E.
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.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613beb3a48190ae3fa9faf15f7122 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:25 a.m.