Triple

T3908321
Position Surface form Disambiguated ID Type / Status
Subject Spiš-Gubałówka Foothills E87258 entity
Predicate namedAfter P63 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š-Gubałówka Foothills, namedAfter, Spiš]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spiš
Context triple: [Spiš-Gubałówka Foothills, namedAfter, 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_69aed9424514819086e9c58adde6652d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeed13bb14819096842c6c82342524 completed March 9, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51caf41c881909c5156480b46e794 completed March 14, 2026, 8:30 a.m.
Created at: March 9, 2026, 3:22 p.m.