Triple

T26365689
Position Surface form Disambiguated ID Type / Status
Subject Altglienicke E660324 entity
Predicate hasBorderHistory P16110 FINISHED
Object inner German border area during Berlin division 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: inner German border area during Berlin division | Statement: [Altglienicke, hasBorderHistory, inner German border area during Berlin division]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderHistory
Context triple: [Altglienicke, hasBorderHistory, inner German border area during Berlin division]
  • A. borderHistory chosen
    Indicates the historical changes, events, or status of borders between entities over time.
  • B. hasSharedBorderHistoryWith
    Indicates that two entities have a history of sharing a common border or boundary at some point in time.
  • C. hasBorderControlHistory
    Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
  • D. hadBorder
    Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
  • E. hasBorderThrough
    Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
  • 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_69ee8126d52c8190bc0b34337c2c9aa8 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f676c440708190a4b9974e95d2291a completed May 2, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f675fd59608190b246383435e68fce completed May 2, 2026, 10:09 p.m.
Created at: April 26, 2026, 10:54 p.m.