Triple
T18935189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Umpqua |
E463224
|
entity |
| Predicate | usesTraditionalWatercraft |
P57914
|
FINISHED |
| Object | dugout canoes |
—
|
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: dugout canoes | Statement: [Lower Umpqua, usesTraditionalWatercraft, dugout canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalWatercraft Context triple: [Lower Umpqua, usesTraditionalWatercraft, dugout canoes]
-
A.
hasTraditionalBoatType
Indicates that an entity is associated with or characterized by a specific traditional type of boat.
-
B.
usesCanoes
chosen
Indicates that one entity makes use of canoes as a means of transport, activity, or operation in relation to another entity or context.
-
C.
usesCrewedBoats
Indicates that an entity performs an activity or operation by employing boats that are crewed by people.
-
D.
hasAncestralCanoe
Indicates that an entity possesses or is associated with a traditional canoe inherited from ancestors or passed down through generations.
-
E.
cannotRideBoats
Indicates that one entity is unable or not permitted to travel or be transported using boats.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e6a8208190973669cae439a91e |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.