Triple

T780342
Position Surface form Disambiguated ID Type / Status
Subject Frankfurt am Main E16481 entity
Predicate locatedIn P40 FINISHED
Object Hesse E14304 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: Hesse | Statement: [Frankfurt am Main, locatedIn, Hesse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hesse
Context triple: [Frankfurt am Main, locatedIn, Hesse]
  • A. Hesse chosen
    Hesse is a federal state in central Germany known for its financial hub Frankfurt am Main and its mix of urban centers, forests, and historic towns.
  • B. South Hesse
    South Hesse is a region in the southern part of the German state of Hesse that includes major urban and economic centers such as Darmstadt and the Rhine-Main area.
  • C. Odenwald
    Odenwald is a low mountain range in southwestern Germany known for its forested hills, historic towns, and scenic hiking landscapes.
  • D. Bavaria
    Bavaria is a historic region and federal state in southeastern Germany, known for its distinct cultural traditions, large size and population, and major cities such as Munich.
  • E. North Hesse
    North Hesse is a region in the northern part of the German state of Hesse, centered around the city of Kassel and known for its forests, hills, and cultural heritage.
  • 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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a750c6708190a3f2c3abf16b4ea4 completed March 1, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac53753d308190928675f60e27d702 completed March 7, 2026, 4:33 p.m.
Created at: March 1, 2026, 7:37 p.m.