Triple

T14322103
Position Surface form Disambiguated ID Type / Status
Subject Colonarie E355114 entity
Predicate inferredPopulationScale P30459 FINISHED
Object village-scale population 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: village-scale population | Statement: [Colonarie, inferredPopulationScale, village-scale population]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inferredPopulationScale
Context triple: [Colonarie, inferredPopulationScale, village-scale population]
  • A. hasPopulationScale
    Indicates the relative size or magnitude of a population associated with an entity, typically expressed as a qualitative or categorical scale.
  • B. peakPopulationApproximate
    Indicates that the peak population of an entity is known only approximately rather than as an exact value.
  • C. populationScale chosen
    Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
  • D. hasPopulationApproximate
    Indicates that an entity has an estimated or approximate population size, rather than an exact count.
  • E. 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.
  • 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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de883bf71c8190a9a092a025cf98f0 completed April 14, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69de2a9515f4819081aabf251bca5878 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:13 a.m.