Triple

T1292446
Position Surface form Disambiguated ID Type / Status
Subject Departmental Council of Allier E27575 entity
Predicate hasDeliberativeAssembly P17337 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: [Departmental Council of Allier, hasDeliberativeAssembly, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDeliberativeAssembly
Context triple: [Departmental Council of Allier, hasDeliberativeAssembly, yes]
  • A. hasPlenaryChamber
    Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
  • B. hasRepresentativeBody
    Indicates that an entity is associated with or governed by a specific representative body that acts or decides on its behalf.
  • C. hasGeneralAssembly chosen
    Indicates that an entity possesses or is associated with a general assembly as its formal deliberative or decision-making body.
  • D. hasLegislatureType
    Indicates the specific form or system of legislature that an entity possesses or operates under.
  • E. hasConsultativeBody
    Indicates that an entity is associated with a consultative body that provides advice, recommendations, or guidance on its decisions or activities.
  • 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_69a496d4ec448190ad653b2590c46711 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c3bb3a9c81909db2ad91defd87b6 completed March 1, 2026, 10:54 p.m.
PD Predicate disambiguation batch_69a4bee64d908190b6a9bb479959d523 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:51 p.m.