Triple

T22435485
Position Surface form Disambiguated ID Type / Status
Subject Ortsbezirk 6 Frankfurt am Main E554610 entity
Predicate contains P35 FINISHED
Object Sindlingen NE NERFINISHED

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: Sindlingen | Statement: [Ortsbezirk 6 Frankfurt am Main, contains, Sindlingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sindlingen
Context triple: [Ortsbezirk 6 Frankfurt am Main, contains, Sindlingen]
  • A. Sindlingen chosen
    Sindlingen is a district in the western part of Frankfurt am Main, Germany, known for its residential character and proximity to industrial areas along the Main River.
  • B. Seßlach
    Seßlach is a small, well-preserved medieval town in northern Bavaria, Germany, known for its intact city walls and historic half-timbered houses.
  • C. Weilersbach
    Weilersbach is a small municipality in the Forchheim district of Bavaria, Germany, known for its rural character and proximity to the Franconian Switzerland region.
  • D. Oßling
    Oßling is a small municipality in the German state of Saxony, located in the eastern part of the country.
  • E. Weßling
    Weßling is a small municipality in Bavaria, Germany, known for its scenic lake and as a residential community near Munich.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15adda0e48190825a5b705ae52d5b completed April 29, 2026, 1:11 a.m.
Created at: April 16, 2026, 8:47 p.m.