Triple

T21233526
Position Surface form Disambiguated ID Type / Status
Subject Geisa E523283 entity
Predicate formerBorderStatus P87896 FINISHED
Object near inner-German border between East and West Germany 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: near inner-German border between East and West Germany | Statement: [Geisa, formerBorderStatus, near inner-German border between East and West Germany]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerBorderStatus
Context triple: [Geisa, formerBorderStatus, near inner-German border between East and West Germany]
  • A. boundaryStatus
    Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
  • B. borderStateOf
    Indicates that one state shares a common boundary or border with another state.
  • C. borderStateOrigin
    Indicates that a state shares a land or maritime border with the place where an entity originated.
  • D. nearFormerBorderWith chosen
    Indicates that one entity is located close to where the former border or boundary with another entity used to be.
  • E. laterFormedBorderBetween
    Indicates that the relationship or boundary between two entities was established at a later time, forming a border between them after an earlier period or state.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734b1524c8190a77eaf2fabd601c3 completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:45 p.m.