Triple
T8033583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duwamish River |
E187046
|
entity |
| Predicate | restorationEffortsBy |
P4089
|
FINISHED |
| Object | local tribes |
—
|
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: local tribes | Statement: [Duwamish River, restorationEffortsBy, local tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationEffortsBy Context triple: [Duwamish River, restorationEffortsBy, local tribes]
-
A.
hasPreservationEfforts
Indicates that actions or measures are being taken to protect, maintain, or restore the condition or existence of something over time.
-
B.
restorationEvent
Indicates an event in which something previously altered, damaged, or degraded is returned to a former or improved state.
-
C.
revitalizationEffort
chosen
Indicates efforts or actions undertaken to restore, renew, or improve the condition, vitality, or functionality of something.
-
D.
revitalizationEffortIn
Indicates that a revitalization effort or improvement initiative is being carried out within a specified location or area.
-
E.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef3e6848190913c4b1bef506aae |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.