Triple

T30804433
Position Surface form Disambiguated ID Type / Status
Subject Lyck E784458 entity
Predicate currentPopulationOfLocationApprox P10175 FINISHED
Object about 60,000 (Ełk, early 21st century) 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: about 60,000 (Ełk, early 21st century) | Statement: [Lyck, currentPopulationOfLocationApprox, about 60,000 (Ełk, early 21st century)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: currentPopulationOfLocationApprox
Context triple: [Lyck, currentPopulationOfLocationApprox, about 60,000 (Ełk, early 21st century)]
  • A. hasPopulationApproximate
    Indicates that an entity has an estimated or approximate population size, rather than an exact count.
  • B. peakPopulationApproximate
    Indicates that the peak population of an entity is known only approximately rather than as an exact value.
  • C. currentPopulation chosen
    Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
  • D. staffPopulationApprox
    Indicates an approximate or estimated number of staff associated with an entity.
  • E. metropolitanAreaPopulationApproximate
    Indicates that the predicate specifies an approximate total population size for a given metropolitan area.
  • 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_69f224b3a7ec819096939414d103e31e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fdbaa226708190b8ed96e93aad38de completed May 8, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69fdb58b07e48190837e00966de050d4 completed May 8, 2026, 10:06 a.m.
Created at: April 29, 2026, 8:42 p.m.