Triple

T35897498
Position Surface form Disambiguated ID Type / Status
Subject Σπιανάδα E1038263 entity
Predicate βρίσκεται στον δήμο P29284 FINISHED
Object Δήμος Κεντρικής Κέρκυρας και Διαποντίων Νήσων 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: Δήμος Κεντρικής Κέρκυρας και Διαποντίων Νήσων | Statement: [Σπιανάδα, βρίσκεται στον δήμο, Δήμος Κεντρικής Κέρκυρας και Διαποντίων Νήσων]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: βρίσκεται στον δήμο
Context triple: [Σπιανάδα, βρίσκεται στον δήμο, Δήμος Κεντρικής Κέρκυρας και Διαποντίων Νήσων]
  • A. находитсяК
    Indicates that one entity is located at, in, or near another entity.
  • B. locatedInMunicipalAssociation
    Indicates that an entity (typically a municipality or locality) is situated within and belongs administratively to a specific municipal association.
  • C. basedInDistrict chosen
    Indicates that an entity is located or has its primary base of operations within a specific administrative district.
  • D. occursInDistrict
    Indicates that an event or activity takes place within the boundaries of a specific district.
  • E. locatedInRegionalCouncil
    Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
  • 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_69f76e2190f88190beb2eed798a4ef01 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7be53890081909b1d93f30a8f31c6 completed May 3, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69f7bccacbac8190978976324c67db28 completed May 3, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:07 p.m.