Triple
T11836429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swinomish Channel |
E281526
|
entity |
| Predicate | dredged |
P31148
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Swinomish Channel, dredged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dredged Context triple: [Swinomish Channel, dredged, true]
-
A.
isDredged
chosen
Indicates that a waterway, channel, or seabed area has been excavated or cleared of sediment or debris, typically to maintain or increase its depth for navigation or other uses.
-
B.
excavated
Indicates that one entity has dug out, uncovered, or removed earth or material from another entity, typically to reveal or extract what lies beneath.
-
C.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
E.
sunk
Indicates that one entity caused another entity to go below the surface of a liquid, typically water, so that it is submerged or destroyed.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62fec0881908c7b89c0b5bcc9a2 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.