Triple

T14430029
Position Surface form Disambiguated ID Type / Status
Subject Württemberg-Weiltingen E357800 entity
Predicate namedAfter P63 FINISHED
Object Weiltingen E877093 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: Weiltingen | Statement: [Württemberg-Weiltingen, namedAfter, Weiltingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weiltingen
Context triple: [Württemberg-Weiltingen, namedAfter, Weiltingen]
  • A. Weiningen
    Weiningen is a small Swiss municipality in the canton of Zurich, located in the Limmat Valley near the city of Zurich.
  • B. Weislingen
    Weislingen is a key antagonist and political rival in Johann Wolfgang von Goethe’s historical drama "Götz von Berlichingen."
  • C. Geilenkirchen
    Geilenkirchen is a town in western Germany best known for hosting a major NATO airbase that serves as the main hub for the alliance’s Airborne Early Warning and Control (AWACS) operations.
  • D. Worringen
    Worringen is a district in the northern part of Cologne, Germany, historically notable as the site of the 1288 Battle of Worringen.
  • E. Wehringen chosen
    Wehringen is a small municipality in Bavaria, Germany, situated in the region surrounding the city of Augsburg.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91154de881909266ae88d1545685 completed April 14, 2026, 7:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bd1c4d0819085edb9ed22128b68 completed May 8, 2026, 3:43 a.m.
Created at: April 10, 2026, 1:18 a.m.