Triple

T35433765
Position Surface form Disambiguated ID Type / Status
Subject Prince-Provostry of Berchtesgaden E1024139 entity
Predicate wasAutonomous P183295 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: [Prince-Provostry of Berchtesgaden, wasAutonomous, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasAutonomous
Context triple: [Prince-Provostry of Berchtesgaden, wasAutonomous, true]
  • A. wasSemiAutonomous
    Indicates that an entity operated with partial self-governance or independent authority while still being subject to a higher controlling power.
  • B. autonomousFor
    Indicates that one entity operates or makes decisions independently on behalf of, or in place of, another specified context, system, or agent.
  • C. sawAutonomyAs
    Indicates viewing or interpreting something (such as a situation, principle, or condition) specifically in terms of autonomy or independent self-governance.
  • D. recognizedAsAutonomousBy
    Indicates that one entity formally acknowledges another entity’s status or operation as independent and self-governing.
  • E. hasAutonomousEntity
    Indicates that one entity possesses, controls, or is associated with another entity that operates autonomously or independently.
  • F. None of above. chosen

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_69f76df743c48190aecb6dd79efb0d95 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79da9f80c8190b0afd8509f28747b completed May 3, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69f79617d40481909ba372f94209c08b completed May 3, 2026, 6:38 p.m.
PDg Predicate description generation batch_69f79da8d8848190ab5ab1bdad95d58c completed May 3, 2026, 7:10 p.m.
Created at: May 3, 2026, 4:04 p.m.