Triple

T37908331
Position Surface form Disambiguated ID Type / Status
Subject Mondsee E945616 entity
Predicate historicalMonasteryType P37070 FINISHED
Object Benedictine monastery (Mondsee Abbey) E1132829 NE 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: Benedictine monastery (Mondsee Abbey) | Statement: [Mondsee, historicalMonasteryType, Benedictine monastery (Mondsee Abbey)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalMonasteryType
Context triple: [Mondsee, historicalMonasteryType, Benedictine monastery (Mondsee Abbey)]
  • A. monasteryType chosen
    Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
  • B. monasteriesAre
    Indicates that a subject is classified as, functions as, or is identified with monasteries.
  • C. monasteryNearbyArchitectureStyle
    Indicates that a monastery is located close to a structure or area characterized by a particular architectural style.
  • D. monasteryEstablished
    Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
  • E. monastery
    Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
  • F. None of above.

Provenance (4 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_69f76ef20bb0819088b5b6ceecb0b8fc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a01c5c5dbb881909b19ba87a7760ee7 completed May 11, 2026, 12:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a412ca0e3948190b1c951ee1298a673 completed June 28, 2026, 2:16 p.m.
PD Predicate disambiguation batch_6a01c549af98819098e0effd775b7710 completed May 11, 2026, 12:02 p.m.
Created at: May 3, 2026, 4:20 p.m.