Triple

T11352924
Position Surface form Disambiguated ID Type / Status
Subject Stolické vrchy E268878 entity
Predicate highestPoint P210 FINISHED
Object Stolica E268884 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: Stolica | Statement: [Stolické vrchy, highestPoint, Stolica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stolica
Context triple: [Stolické vrchy, highestPoint, Stolica]
  • A. Stolica chosen
    Stolica is the highest peak of the Slovak Ore Mountains in central Slovakia, known for its forested slopes and scenic hiking routes.
  • B. Ostan
    Ostan was a historic city that served as the political and administrative center of the medieval Armenian region of Vaspurakan.
  • C. Karlov
    Karlov is a historic university campus complex in Prague that houses several faculties of Charles University, particularly in the medical and natural sciences.
  • D. Oras
    Oras is a coastal municipality in the province of Eastern Samar in the Philippines, known for its rural communities and Pacific shoreline.
  • E. Raška
    Raška is a historical region in southwestern Serbia regarded as the medieval heartland of the early Serbian state and Orthodox monastic culture.
  • 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_69d6aacbe18081909e5fadb50082dd96 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea24489081908fbf47fd2e6d709c completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e543a6e97481909dc77a553b217b4d completed April 19, 2026, 9:05 p.m.
Created at: April 8, 2026, 9:33 p.m.