Triple

T12754397
Position Surface form Disambiguated ID Type / Status
Subject Lučenec E304819 entity
Predicate locatedIn P40 FINISHED
Object Novohrad E281399 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: Novohrad | Statement: [Lučenec, locatedIn, Novohrad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Novohrad
Context triple: [Lučenec, locatedIn, Novohrad]
  • A. Novohrad chosen
    Novohrad is a historical and geographical region in southern Slovakia known for its rural landscapes, traditional culture, and border location near Hungary.
  • B. Nové Zámky
    Nové Zámky is a town in southern Slovakia known as a regional center on the Nitra River with historical fortifications and a mixed Slovak-Hungarian cultural heritage.
  • C. Nové Hrady
    Nové Hrady is a historic town in the Czech Republic known for its well-preserved castle and location near the Austrian border in the South Bohemian Region.
  • D. Nový Bor
    Nový Bor is a Czech town in the Liberec Region known historically for its glassmaking industry and proximity to the Lusatian Mountains.
  • E. Nové Mesto
    Nové Mesto is a borough of Bratislava, Slovakia, known for its mix of residential areas, sports facilities, and commercial zones.
  • 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c9aa6308190bfcb1511a561c0f9 completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:27 p.m.