Triple

T2201259
Position Surface form Disambiguated ID Type / Status
Subject Pawnee E50493 entity
Predicate estimatedPopulationCirca1800 P3412 FINISHED
Object 10000–12000 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: 10000–12000 | Statement: [Pawnee, estimatedPopulationCirca1800, 10000–12000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: estimatedPopulationCirca1800
Context triple: [Pawnee, estimatedPopulationCirca1800, 10000–12000]
  • A. hasPopulationAsOf
    Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
  • B. formerPopulation
    Indicates that an entity once had a certain population value or size during a past time period but no longer does.
  • C. hasPopulationApproximate chosen
    Indicates that an entity has an estimated or approximate population size, rather than an exact count.
  • D. foundingPopulation
    Indicates the population size or composition present at the time an entity (such as a settlement, organization, or species group) was originally founded or established.
  • E. permanentPopulation
    Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
  • 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_69a88b044ab48190add007487680f009 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfa1b41c8190b0f7467d0dcdfbcd completed March 7, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69abbda706f4819094de73e1d1d1f539 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.