Triple

T19055758
Position Surface form Disambiguated ID Type / Status
Subject Plains Miwok culture E466389 entity
Predicate reliesOnResource P22819 FINISHED
Object Valley oak acorns 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: Valley oak acorns | Statement: [Plains Miwok culture, reliesOnResource, Valley oak acorns]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reliesOnResource
Context triple: [Plains Miwok culture, reliesOnResource, Valley oak acorns]
  • A. reliedOn chosen
    Indicates that one entity depends on another for support, resources, or functionality.
  • B. basedOnResource
    Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
  • C. conceptuallyDependsOn
    Indicates that one entity’s definition, validity, or understanding relies on or is grounded in the concepts provided by another entity.
  • D. kernelDependsOn
    Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
  • E. associatedWithResource
    Indicates a relationship in which an entity is linked or connected to a particular resource, such that the resource is relevant or applicable to that entity.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5dc056b708190a2b84cbddf0fc2d9 completed April 20, 2026, 7:55 a.m.
PD Predicate disambiguation batch_69e4b99633c8819097988608c278ecf8 completed April 19, 2026, 11:16 a.m.
Created at: April 10, 2026, 12:03 p.m.