Triple

T10312686
Position Surface form Disambiguated ID Type / Status
Subject Košice Zoo E241933 entity
Predicate hasApproximateRanking P93314 FINISHED
Object one of the largest zoos in Slovakia by area 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: one of the largest zoos in Slovakia by area | Statement: [Košice Zoo, hasApproximateRanking, one of the largest zoos in Slovakia by area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateRanking
Context triple: [Košice Zoo, hasApproximateRanking, one of the largest zoos in Slovakia by area]
  • A. hasRankingFactor
    Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
  • B. hasRankingAlgorithm
    Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
  • C. hasComparableRank
    Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
  • D. hasRankingUnit
    Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
  • E. hasRankOrder
    Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
  • F. None of above. chosen

Provenance (4 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_69d381ac38808190a8ca7457c85b625b completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d7ccb7ec8190a538cf279e48116e completed April 7, 2026, 10:09 a.m.
PD Predicate disambiguation batch_69d4d1f4f354819080b4ed4bc61bdff6 completed April 7, 2026, 9:44 a.m.
PDg Predicate description generation batch_69d4d7cada7881908beba55a1dc9ecb9 completed April 7, 2026, 10:09 a.m.
Created at: April 6, 2026, 11:48 a.m.