Triple

T10068801
Position Surface form Disambiguated ID Type / Status
Subject Hoechst E213164 entity
Predicate headquartersDistrict P40148 FINISHED
Object Höchst E131174 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: Höchst | Statement: [Hoechst, headquartersDistrict, Höchst]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Höchst
Context triple: [Hoechst, headquartersDistrict, Höchst]
  • A. Höchst
    Höchst is a municipality in the Austrian state of Vorarlberg, located near the Swiss border along the Rhine River.
  • B. Höchst chosen
    Höchst is a historic district in western Frankfurt am Main, Germany, known for its well-preserved old town and former industrial and chemical industry sites.
  • C. Oststadt
    Oststadt is a central district of Hanover, Germany, known for its urban residential areas, cultural venues, and proximity to the city’s main commercial and administrative centers.
  • D. Unterhaching
    Unterhaching is a municipality in Bavaria, Germany, located just south of Munich and known for its residential character and local football club, SpVgg Unterhaching.
  • E. Grevesmühlen
    Grevesmühlen is a small town in the German state of Mecklenburg-Vorpommern, known as a local administrative and service center in the north of the country.
  • 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_69ca83977128819084084eb7d1d8c52a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcff8d9c08190bc030f1dcc696310 completed April 2, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d29a96fc888190aec7cd364a0d7fb1 completed April 5, 2026, 5:23 p.m.
Created at: March 30, 2026, 8:58 p.m.