Triple

T16987891
Position Surface form Disambiguated ID Type / Status
Subject St. Marien church (Marienberg) E412116 entity
Predicate locatedIn P40 FINISHED
Object Marienberg E84126 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: Marienberg | Statement: [St. Marien church (Marienberg), locatedIn, Marienberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marienberg
Context triple: [St. Marien church (Marienberg), locatedIn, Marienberg]
  • A. Marienberg chosen
    Marienberg is a historic mining town in Saxony, Germany, known for its Renaissance-era planned layout and location in the central Ore Mountains.
  • B. Marienberg hill
    Marienberg hill is a prominent elevation overlooking Würzburg, Germany, best known as the site of the historic Marienberg Fortress.
  • C. Falkenfels
    Falkenfels is a small municipality in the district of Straubing-Bogen in the Bavarian region of Germany.
  • D. Riffelberg
    Riffelberg is a scenic mountain stop in the Swiss Alps near Zermatt, known for its panoramic views of the Matterhorn and surrounding peaks.
  • E. Herisau
    Herisau is a Swiss town that serves as the administrative and economic center of the canton of Appenzell Ausserrhoden.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d27cd2048190800a60ae653e11e1 completed April 18, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b433e688190ac8dda10638a197f completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:32 a.m.