Triple

T33274512
Position Surface form Disambiguated ID Type / Status
Subject Cassovia E851866 entity
Predicate regionOfModernEquivalent P32046 FINISHED
Object Košice Region NE NERFINISHED

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: Košice Region | Statement: [Cassovia, regionOfModernEquivalent, Košice Region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionOfModernEquivalent
Context triple: [Cassovia, regionOfModernEquivalent, Košice Region]
  • A. locatedInModernAdministrativeRegion chosen
    Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
  • B. historicalRegionNowInCountry
    Indicates that a historical region is currently located within the borders or jurisdiction of a specified modern country.
  • C. modernNameOfArea
    Indicates that one area entity represents the current or modern name of another area entity.
  • D. historicalRegionCorrespondsTo
    Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
  • E. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • 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_69f349653da08190819876015a298fdb completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff1f3f94fc819095955299f50ab4ce completed May 9, 2026, 11:49 a.m.
PD Predicate disambiguation batch_69ff1ea47748819082f63d9b9d9c3e65 completed May 9, 2026, 11:46 a.m.
Created at: May 1, 2026, 1:32 a.m.