Triple

T3710674
Position Surface form Disambiguated ID Type / Status
Subject Spiš highlanders E81402 entity
Predicate ethnographicRegion P1968 FINISHED
Object Spiš E129227 NE 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: Spiš | Statement: [Spiš highlanders, ethnographicRegion, Spiš]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spiš
Context triple: [Spiš highlanders, ethnographicRegion, Spiš]
  • A. Spiš chosen
    Spiš is a historical region in northeastern Slovakia and southeastern Poland, known for its medieval towns, castles, and rich cultural heritage.
  • B. Spišská Nová Ves
    Spišská Nová Ves is a town in eastern Slovakia known as a cultural and economic center of the Spiš region and as a gateway to the Slovak Paradise National Park.
  • C. Spiš Castle
    Spiš Castle is one of the largest castle complexes in Central Europe and a UNESCO World Heritage Site located in eastern Slovakia.
  • D. Prešporok
    Prešporok is the historical Slovak name for the city now known as Bratislava, the capital of Slovakia.
  • E. Trebišov
    Trebišov is a town in eastern Slovakia known as an administrative and cultural center of the Trebišov District.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad8b1a81588190b3f27a5483bb610e completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc584b86c8190ba1a1073da440b07 completed March 8, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4ce052660819089ad899a20b8a720 completed March 14, 2026, 2:55 a.m.
Created at: March 8, 2026, 3:33 p.m.