Triple

T35304183
Position Surface form Disambiguated ID Type / Status
Subject Wupatki Pueblo E1019587 entity
Predicate maxPopulationEstimate P101078 FINISHED
Object several hundred inhabitants 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: several hundred inhabitants | Statement: [Wupatki Pueblo, maxPopulationEstimate, several hundred inhabitants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maxPopulationEstimate
Context triple: [Wupatki Pueblo, maxPopulationEstimate, several hundred inhabitants]
  • A. peakPopulationApproximate chosen
    Indicates that the peak population of an entity is known only approximately rather than as an exact value.
  • B. envisionedPopulation
    Indicates a relationship where an entity specifies or projects an expected or target population size for something (such as a place, project, or scenario).
  • C. populationAtPeak
    Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
  • D. plannedPopulation
    Indicates the intended or projected number of individuals expected to occupy or use something, such as a facility, area, or system, according to a plan.
  • E. hasPopulationApproximate
    Indicates that an entity has an estimated or approximate population size, rather than an exact count.
  • 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_69f76de8b4c48190ae504b86185c474c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7904d95b48190b98dca59dbb592d8 completed May 3, 2026, 6:13 p.m.
PD Predicate disambiguation batch_69f78e2f52e08190a77661223a96c601 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:03 p.m.