Triple

T19373396
Position Surface form Disambiguated ID Type / Status
Subject Colville people E484601 entity
Predicate usesTraditionalTechnology P124889 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: [Colville people, usesTraditionalTechnology, dugout canoes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTraditionalTechnology
Context triple: [Colville people, usesTraditionalTechnology, dugout canoes]
  • A. hasTraditionalTechnology chosen
    Indicates that an entity possesses, uses, or is associated with technology rooted in longstanding, customary, or indigenous practices rather than modern or industrial methods.
  • B. laterUsedTechnology
    Indicates that one entity adopted or employed a technology after another entity had already used it.
  • C. formerTechnology
    Indicates that an entity previously used or was associated with a particular technology but no longer is.
  • D. hasTraditionalFeatures
    Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
  • E. isTraditional
    Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
  • 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61a59f8cc8190b314cba95c25f2a0 completed April 20, 2026, 12:21 p.m.
PD Predicate disambiguation batch_69e4fd54f8e48190956e73dd8969164a completed April 19, 2026, 4:05 p.m.
Created at: April 10, 2026, 1:35 p.m.