Triple

T1358852
Position Surface form Disambiguated ID Type / Status
Subject Count of Vechta E29051 entity
Predicate hasTerritorialBase P21614 FINISHED
Object territory around the town of Vechta 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: territory around the town of Vechta | Statement: [Count of Vechta, hasTerritorialBase, territory around the town of Vechta]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialBase
Context triple: [Count of Vechta, hasTerritorialBase, territory around the town of Vechta]
  • A. hasTerritorialAssociation chosen
    Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
  • B. hasMilitaryBase
    Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
  • C. locatedOnTerritoryOf
    Indicates that one entity is situated within or on the land area governed or owned by another entity.
  • D. hasOverseasPresenceIn
    Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
  • E. appliesToTerritorialEntity
    Indicates that something (such as a rule, measure, status, or attribute) is valid for, relevant to, or in effect within a specific territorial entity.
  • 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_69a498d77abc8190913bf57e5f51d2c4 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c290db288190910fcfa17e902663 completed March 1, 2026, 10:49 p.m.
PD Predicate disambiguation batch_69a4bef7700c819099b294e8d9320e70 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:56 p.m.