Triple

T1292428
Position Surface form Disambiguated ID Type / Status
Subject Departmental Council of Allier E27575 entity
Predicate hasExecutiveFunction P17162 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, hasExecutiveFunction, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExecutiveFunction
Context triple: [Departmental Council of Allier, hasExecutiveFunction, yes]
  • A. hasExecutiveSeat
    Indicates that an entity holds a position or seat with executive authority or decision-making power within an organization or governing body.
  • B. hasCommitteeFunction
    Indicates that a committee is assigned or performs a specific function, role, or responsibility.
  • C. hadExecutivePowerIn
    Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
  • D. hasCivicFunction chosen
    Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
  • E. hasChiefExecutiveRole
    Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
  • 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.