Triple

T6259286
Position Surface form Disambiguated ID Type / Status
Subject Sanz E140252 entity
Predicate hasDescendantDynasty P13166 FINISHED
Object Gorlitz E32852 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: Gorlitz | Statement: [Sanz, hasDescendantDynasty, Gorlitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gorlitz
Context triple: [Sanz, hasDescendantDynasty, Gorlitz]
  • A. Görlitz chosen
    Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
  • B. Oppeln
    Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
  • C. Bautzen
    Bautzen is a historic town in eastern Germany known for its well-preserved medieval architecture and as a cultural center of the Sorbian minority.
  • D. Liebenwalde
    Liebenwalde is a small town and municipality in the Oberhavel district of the German state of Brandenburg.
  • E. Glogau
    Glogau is the German name for the town of Głogów, a historic city in southwestern Poland on the Oder River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c008c95c5c819084bd3dd56133d84d completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06383616c819090c7994740317564 completed March 22, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69c603ee891481909f640f54b70f9d60 completed March 27, 2026, 4:13 a.m.
Created at: March 22, 2026, 4:24 p.m.