Triple

T4393030
Position Surface form Disambiguated ID Type / Status
Subject Gemeinderat (Bern) E99409 entity
Predicate isCollegialBody P28340 FINISHED
Object true 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: true | Statement: [Gemeinderat (Bern), isCollegialBody, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCollegialBody
Context triple: [Gemeinderat (Bern), isCollegialBody, true]
  • A. isCollegialWith
    Indicates a relationship where two entities interact in a cooperative, respectful, and professionally friendly manner, typically as peers or colleagues.
  • B. isCollegiateBodyOf chosen
    Indicates that one entity functions as the collegiate governing or decision-making body associated with another entity, such as an institution or organization.
  • C. isElectedBody
    Indicates that an entity is a formal decision-making group whose members attain their positions through an election process.
  • D. isClericalBodyFor
    Indicates that one entity functions as the official clerical or administrative body responsible for serving, supporting, or governing another entity.
  • E. sharesCollegialBodyWith
    Indicates that two entities are members of, or participate together in, the same collegial body or collective decision-making group.
  • 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_69b345506b408190b0e3dee616738a7d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b352a8862481909dc67abf42be6928 completed March 12, 2026, 11:56 p.m.
PD Predicate disambiguation batch_69b34f572efc8190bad1e5078cbcb75a completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:19 p.m.