Triple

T20801613
Position Surface form Disambiguated ID Type / Status
Subject Paide E512053 entity
Predicate hasLandmark P105 FINISHED
Object Paide Castle NE NERFINISHED

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: Paide Castle | Statement: [Paide, hasLandmark, Paide Castle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paide Castle
Context triple: [Paide, hasLandmark, Paide Castle]
  • A. Paide Castle chosen
    Paide Castle is a historic medieval fortress in Paide, Estonia, known for its distinctive limestone tower and role in the region’s defensive history.
  • B. Kuressaare Castle
    Kuressaare Castle is a well-preserved medieval stone fortress and former bishop’s residence located in the town of Kuressaare on Saaremaa Island in Estonia.
  • C. Haapsalu Castle
    Haapsalu Castle is a medieval fortress in western Estonia renowned for its well-preserved ruins, historic cathedral, and the legend of the White Lady.
  • D. Rakvere Castle
    Rakvere Castle is a medieval fortress and popular historical attraction located in the town of Rakvere in northern Estonia.
  • E. Turaida Castle
    Turaida Castle is a medieval red-brick fortress in Sigulda, Latvia, renowned as a major historical and architectural landmark in the Vidzeme region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4cc69f481908e98751e697b9df4 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2b0d75881909cc89ebe4e27adc1 completed April 21, 2026, 12:20 a.m.
Created at: April 16, 2026, 12:39 p.m.