Triple

T88581
Position Surface form Disambiguated ID Type / Status
Subject Central Valley E1779 entity
Predicate historicalInhabitants P3032 FINISHED
Object Native American peoples 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: Native American peoples | Statement: [Central Valley, historicalInhabitants, Native American peoples]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalInhabitants
Context triple: [Central Valley, historicalInhabitants, Native American peoples]
  • A. historicallyInhabitedBy chosen
    Indicates that a place or region was inhabited by a particular group or population during some period in the past.
  • B. occupationPeriod
    Indicates the time span during which an entity holds or held a particular occupation or role.
  • C. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • D. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • E. historicalOrigin
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another 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_69a24d1a97dc819094e6c021fe9b05a7 completed Feb. 28, 2026, 2:04 a.m.
NER Named-entity recognition batch_69a2503d304c8190a0034ffa4a38a501 completed Feb. 28, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69a24eb6da2c8190a33d144d219f7abe completed Feb. 28, 2026, 2:11 a.m.
Created at: Feb. 28, 2026, 2:07 a.m.