Triple

T1334006
Position Surface form Disambiguated ID Type / Status
Subject Lord of Ahaus E28705 entity
Predicate hasTerritorialScope P8868 FINISHED
Object Ahaus and environs 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: Ahaus and environs | Statement: [Lord of Ahaus, hasTerritorialScope, Ahaus and environs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialScope
Context triple: [Lord of Ahaus, hasTerritorialScope, Ahaus and environs]
  • A. 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.
  • B. territorialExtent chosen
    Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
  • C. hasTerritorialAssociation
    Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
  • D. appliesToAdministrativeTerritory
    Indicates that something (such as a rule, measure, or status) is valid for, relevant to, or in force within a specific administrative territory.
  • E. entailsTerritorialDesignation
    Indicates that one entity’s status, action, or condition necessarily results in or includes a specific territorial designation being applied or recognized.
  • 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_69a498561a508190a3e1bc137c2b866a completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1e98900819092c54c0fb58b958a completed March 1, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69a4bef174708190a07bbc697fe19a2d completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:55 p.m.