Triple

T14024017
Position Surface form Disambiguated ID Type / Status
Subject Wielki Giewont E337408 entity
Predicate hasPart P35 FINISHED
Object Middle Giewont E67652 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: Middle Giewont | Statement: [Wielki Giewont, hasPart, Middle Giewont]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Middle Giewont
Context triple: [Wielki Giewont, hasPart, Middle Giewont]
  • A. Middleside
    Middleside is a district or area within Fort Mills, historically associated with the British military presence on Hong Kong’s Stonecutters Island.
  • B. Giewont chosen
    Giewont is a prominent, cross-topped mountain massif in the Polish Tatra Mountains, famed as a national symbol and popular hiking destination overlooking the town of Zakopane.
  • C. Mittelhaardt
    Mittelhaardt is a renowned wine-growing area within Germany’s Palatinate (Pfalz) region, noted especially for its high-quality Riesling vineyards.
  • D. Noghere
    Noghere is a locality within the municipality of Muggia in northeastern Italy, near the Gulf of Trieste.
  • E. Mitte
    Mitte is the central district of Berlin, Germany, known as the historic core of the city and home to many major landmarks and government institutions.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3d87b88190b038d334f4965369 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc33170ec8190b0ffe41a567a590b completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:19 p.m.