Triple

T792242
Position Surface form Disambiguated ID Type / Status
Subject Monmouthshire County Council E16939 entity
Predicate hasCeremonialHead P3343 FINISHED
Object Chair of the Council 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: Chair of the Council | Statement: [Monmouthshire County Council, hasCeremonialHead, Chair of the Council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCeremonialHead
Context triple: [Monmouthshire County Council, hasCeremonialHead, Chair of the Council]
  • A. ceremonialUse
    Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
  • B. ceremonialDressFeature
    Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
  • C. ceremonialRole chosen
    Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
  • D. ceremonialOrigin
    Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
  • E. ceremonialAssociation
    Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
  • 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_69a4936cb7448190914f5fe4b8d81607 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a798c7608190b9c79c52a1fe0859 completed March 1, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69a4a510f61881909175d6d8719246cd completed March 1, 2026, 8:44 p.m.
Created at: March 1, 2026, 7:38 p.m.