Triple

T21656064
Position Surface form Disambiguated ID Type / Status
Subject Almopia E534469 entity
Predicate hasMajorTown P316 FINISHED
Object Prosotsani 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: Prosotsani | Statement: [Almopia, hasMajorTown, Prosotsani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prosotsani
Context triple: [Almopia, hasMajorTown, Prosotsani]
  • A. Prosotsani chosen
    Prosotsani is a town and municipality in northern Greece, situated in the Drama regional unit of Eastern Macedonia and Thrace.
  • B. Orlovets
    Orlovets is a prominent mountain peak in Bulgaria’s Rila Mountains, popular with hikers and climbers for its rugged alpine terrain and scenic views.
  • C. Pavlikeni
    Pavlikeni is a small town in northern Bulgaria known for its agricultural surroundings and local pottery traditions.
  • D. Potaissa
    Potaissa is the ancient Roman name of the modern city of Turda in present-day Romania, known historically as a significant military and administrative center in the province of Dacia.
  • E. Volosko
    Volosko is a historic coastal village and former fishing port on the Adriatic Sea, now part of the town of Opatija in western Croatia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef59185b208190a2cf4b8f54a2c231 completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:36 p.m.