Triple

T26221411
Position Surface form Disambiguated ID Type / Status
Subject Kaunitz family E655771 entity
Predicate territorialConnection P21614 FINISHED
Object County of Rietberg 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: County of Rietberg | Statement: [Kaunitz family, territorialConnection, County of Rietberg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: territorialConnection
Context triple: [Kaunitz family, territorialConnection, County of Rietberg]
  • A. hasTerritorialAssociation chosen
    Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
  • B. territoryCorrespondedTo
    Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
  • C. hasGeographicConnectionTo
    Indicates a relationship where two entities are linked through a shared or relevant geographic feature, location, or spatial association.
  • D. territorialLevel
    Indicates the administrative or geographic tier at which something is defined, applied, or governed within a territorial hierarchy.
  • E. territoryFeature
    Indicates that a specific geographic or physical feature is located within, characterizes, or is part of a given territory.
  • 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_69ee5b4a77e08190bfcb5f8ecdc55abd completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f62d89b89c8190afb372a8172111e7 completed May 2, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69f62c1379f08190836c3e02b0c892df completed May 2, 2026, 4:53 p.m.
Created at: April 26, 2026, 8:56 p.m.