Triple

T34321612
Position Surface form Disambiguated ID Type / Status
Subject Koewacht E880748 entity
Predicate locatedInAdminArea P71092 FINISHED
Object Terneuzen E252140 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: Terneuzen | Statement: [Koewacht, locatedInAdminArea, Terneuzen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInAdminArea
Context triple: [Koewacht, locatedInAdminArea, Terneuzen]
  • A. isLocatedInAdministrativeArea chosen
    Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
  • B. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • C. partlyInAdministrativeArea
    Indicates that an entity is located such that only a portion of it lies within a specified administrative area (e.g., a city, county, or region).
  • D. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • E. administersAreaType
    Indicates that a governing body or authority is responsible for managing or overseeing a specific type or category of geographic or administrative area.
  • 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_69f349b9cd508190a996a616903b3e6d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a45de0026148190bed57ae1a6231ce6 completed July 2, 2026, 3:41 a.m.
PD Predicate disambiguation batch_6a0379fbe4a08190bfe65ebd141164e9 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:57 a.m.