Triple

T5074458
Position Surface form Disambiguated ID Type / Status
Subject Maribor E114358 entity
Predicate hasPopulationRankInSlovenia P25930 FINISHED
Object 2 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: 2 | Statement: [Maribor, hasPopulationRankInSlovenia, 2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPopulationRankInSlovenia
Context triple: [Maribor, hasPopulationRankInSlovenia, 2]
  • 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. hasPopulationRankInSwitzerland
    Indicates the relative position of an entity in the ordered list of populations within Switzerland, such as its rank by population size compared to other Swiss entities.
  • E. hasPopulationRankInChile
    Indicates the relative position of an entity in the ordered ranking of populations within Chile.
  • 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_69bd443cf28c8190ad371d603563dbdd completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd74d0be1c819081b26235fe602a30 completed March 20, 2026, 4:24 p.m.
PD Predicate disambiguation batch_69bd7157fe608190b4515d56fdd0a616 completed March 20, 2026, 4:10 p.m.
Created at: March 20, 2026, 1:39 p.m.