Triple

T33699281
Position Surface form Disambiguated ID Type / Status
Subject SI-112 (Municipality of Sevnica) E863408 entity
Predicate hasTerritorialUnitSeat P15510 FINISHED
Object Sevnica 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: Sevnica | Statement: [SI-112 (Municipality of Sevnica), hasTerritorialUnitSeat, Sevnica]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialUnitSeat
Context triple: [SI-112 (Municipality of Sevnica), hasTerritorialUnitSeat, Sevnica]
  • A. hasSeatOfAdministration
    Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
  • B. hasMunicipalLeaderSeat
    Indicates that a specific location serves as the official seat or office location of a municipal leader (e.g., mayor) for a municipality.
  • C. municipalitySeat chosen
    Indicates that one entity serves as the administrative center or capital (seat) of a municipality.
  • D. hasTownshipSeat
    Indicates that a particular location serves as the administrative or governing center (seat) of a specified township.
  • E. mainSeatOf
    Indicates that one entity serves as the primary or central seat (e.g., of government, administration, or authority) for another entity.
  • 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_69f3498723a08190ac034339cc78eade completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fdb31800508190beec15adb9bbd292 completed May 8, 2026, 9:55 a.m.
PD Predicate disambiguation batch_69fdb19c381c8190bafb2f565da097f1 completed May 8, 2026, 9:49 a.m.
Created at: May 1, 2026, 1:43 a.m.