Triple

T736524
Position Surface form Disambiguated ID Type / Status
Subject Kaunas E14945 entity
Predicate isMunicipalityType P10835 FINISHED
Object city municipality LITERAL 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: city municipality | Statement: [Kaunas, isMunicipalityType, city municipality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMunicipalityType
Context triple: [Kaunas, isMunicipalityType, city municipality]
  • A. hasMunicipalityType chosen
    Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
  • B. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • C. municipality
    Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
  • D. specialMunicipality
    Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
  • E. isSubProvincialCity
    Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
  • 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_69a4934d9930819099eed80096b0597d completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a66820548190b373deb117187c2c completed March 1, 2026, 8:49 p.m.
PD Predicate disambiguation batch_69a4a4fafee081909bf356854c09aaff completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.