Triple

T35230778
Position Surface form Disambiguated ID Type / Status
Subject Imperial City of Reutlingen E1017226 entity
Predicate hasBurgomaster P185 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: [Imperial City of Reutlingen, hasBurgomaster, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBurgomaster
Context triple: [Imperial City of Reutlingen, hasBurgomaster, yes]
  • A. hasMayor chosen
    Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
  • B. hasBurgee
    Indicates that an entity possesses or is associated with a specific burgee (a distinguishing flag, typically used by clubs or vessels).
  • C. hasCityManager
    Indicates that an entity has a specific individual who serves in the role of city manager for it.
  • D. hasBoroughPresident
    Indicates that a borough is associated with a specific individual who serves as its president or chief elected official.
  • E. hasBoroughCouncil
    Indicates that an administrative area is governed or overseen by a specific borough council.
  • 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:02 p.m.