Triple

T31254880
Position Surface form Disambiguated ID Type / Status
Subject Verwaltungsgemeinschaft Schondorf am Ammersee E796930 entity
Predicate sharesAdministrativeServicesFor P45995 FINISHED
Object Schondorf am Ammersee NE NERFINISHED

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: Schondorf am Ammersee | Statement: [Verwaltungsgemeinschaft Schondorf am Ammersee, sharesAdministrativeServicesFor, Schondorf am Ammersee]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesAdministrativeServicesFor
Context triple: [Verwaltungsgemeinschaft Schondorf am Ammersee, sharesAdministrativeServicesFor, Schondorf am Ammersee]
  • A. sharesAdministrationWith chosen
    Indicates that two entities are jointly managed, governed, or overseen by the same administrative body or authority.
  • B. sharesServicesWith
    Indicates that two entities make use of, provide, or are connected through the same services or service infrastructure.
  • C. administersFor
    Indicates that one entity provides or applies something (such as a treatment, service, or resource) on behalf of or for the benefit of another entity.
  • D. sharesDivisionWith
    Indicates that two entities belong to or operate within the same organizational division.
  • E. sharesAppointmentProcedureWith
    Indicates that two or more entities are associated with the same appointment procedure, implying they follow or participate in an identical scheduled process or protocol.
  • 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_69f224dd5fdc81908a4cd24917b67668 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fec8aef1d8819094c7fd7074038e6b completed May 9, 2026, 5:39 a.m.
PD Predicate disambiguation batch_69fec639876481908efd84a3631a4271 completed May 9, 2026, 5:29 a.m.
Created at: April 29, 2026, 9:12 p.m.