Triple

T18368680
Position Surface form Disambiguated ID Type / Status
Subject Multnomah dialect E440119 entity
Predicate spokenInPastTense P130839 FINISHED
Object was traditionally spoken along the lower Columbia River 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: was traditionally spoken along the lower Columbia River | Statement: [Multnomah dialect, spokenInPastTense, was traditionally spoken along the lower Columbia River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spokenInPastTense
Context triple: [Multnomah dialect, spokenInPastTense, was traditionally spoken along the lower Columbia River]
  • A. usedInPastBy
    Indicates that an entity was previously utilized or employed by another entity at some time in the past.
  • B. operatedInThePastTense
    Indicates that the action of operating was performed by the subject in the past.
  • C. spokenUntil
    Indicates that an act of speaking or verbal communication continues up to a specific time or event and then stops.
  • D. hasPastTenseEnding
    Indicates that a verb form ends with a morphological marker typically used to express past tense.
  • E. spokenForm
    Indicates the way something is pronounced or expressed in spoken language, as opposed to its written or symbolic form.
  • F. None of above. chosen

Provenance (4 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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e51750d3dc8190b153046c1171ee2b completed April 19, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69e44fed3fdc81908f4ed6a81db42416 completed April 19, 2026, 3:45 a.m.
PDg Predicate description generation batch_69e451a1bda48190a9cd1db436d4be62 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 10:38 a.m.