Triple
T2876088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duwamish people |
E56880
|
entity |
| Predicate | traditionalTransportation |
P1379
|
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: [Duwamish people, traditionalTransportation, dugout canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTransportation Context triple: [Duwamish people, traditionalTransportation, dugout canoes]
-
A.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
B.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
C.
transportationContext
Indicates the situational or environmental conditions under which transportation occurs, such as mode, purpose, or circumstances of travel.
-
D.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0061d048190bb1e5a01e7ceb0e2 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.