Triple

T2875938
Position Surface form Disambiguated ID Type / Status
Subject Gomel E56876 entity
Predicate hasPopulationRankInBelarus P25930 FINISHED
Object second largest city 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: second largest city | Statement: [Gomel, hasPopulationRankInBelarus, second largest city]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPopulationRankInBelarus
Context triple: [Gomel, hasPopulationRankInBelarus, second largest city]
  • A. hasPopulationRankInEstonia
    Indicates the relative position of an entity in the ordered list of populations within Estonia, such as its rank by population size compared to other entities in the country.
  • B. hasPopulationRank
    Indicates the relative position of an entity in an ordered list based on the size of its population.
  • C. hasPopulationRankInRegion chosen
    Indicates that an entity has a specific population-based rank or position within a defined geographic region.
  • D. populationRankInUkraine
    Indicates the relative position of an entity in terms of population size compared to other entities within Ukraine.
  • E. populationRankInLithuania
    Indicates the relative position of an entity in terms of population size compared to other entities within Lithuania.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe0061d048190bb1e5a01e7ceb0e2 completed March 7, 2026, 8:21 a.m.
PD Predicate disambiguation batch_69abdd142e4c8190b424cb0c5ff40d04 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:03 p.m.