Triple

T12919473
Position Surface form Disambiguated ID Type / Status
Subject Izmir Metropolitan Municipal Council E309075 entity
Predicate hasExtraordinarySessions P4271 FINISHED
Object yes 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: yes | Statement: [Izmir Metropolitan Municipal Council, hasExtraordinarySessions, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExtraordinarySessions
Context triple: [Izmir Metropolitan Municipal Council, hasExtraordinarySessions, yes]
  • A. hasExtraordinaryExercise
    Indicates that an entity engages in an unusually intense, prolonged, or otherwise exceptional level of physical exercise beyond typical norms.
  • B. hasAfterHoursSession
    Indicates that an entity conducts or participates in a session that takes place outside of regular or standard operating hours.
  • C. canHoldSpecialSessions chosen
    Indicates that an entity has the authority or capability to convene special or extraordinary sessions outside the regular schedule.
  • D. hasPlenarySessions
    Indicates that an event or organization includes formal plenary sessions as part of its activities or structure.
  • E. hasOccasionalEvent
    Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
  • 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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d971e6d9fc8190b8a5244b26b5f78a completed April 10, 2026, 9:55 p.m.
PD Predicate disambiguation batch_69d96fa9b7708190a9e9fa30f59ff580 completed April 10, 2026, 9:46 p.m.
Created at: April 9, 2026, 5:41 p.m.