Triple

T5622859
Position Surface form Disambiguated ID Type / Status
Subject Willebrord Snellius E147648 entity
Predicate deathPlace P21 FINISHED
Object Leiden E14108 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: Leiden | Statement: [Willebrord Snellius, deathPlace, Leiden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leiden
Context triple: [Willebrord Snellius, deathPlace, Leiden]
  • A. Leiden chosen
    Leiden is a historic Dutch city in South Holland known for its prestigious university, rich cultural heritage, and well-preserved canals and old town.
  • B. Utrecht
    Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
  • C. Nijmegen
    Nijmegen is a historic Dutch city near the German border that played a crucial strategic role during World War II, particularly in the Allied advance in 1944.
  • D. Groningen
    Groningen is a historic province in the northern Netherlands, known for its university city of the same name, flat landscapes, and rich maritime and agricultural heritage.
  • E. Haarlem
    Haarlem is a historic Dutch city in the province of North Holland, known for its medieval architecture, cultural heritage, and role as a regional center near Amsterdam.
  • 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_69c00906f2a88190a992c66b13d606d4 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c02214b4948190b71a9f59499092f6 completed March 22, 2026, 5:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c94daace8081908b07274ab876faea completed March 29, 2026, 4:04 p.m.
Created at: March 22, 2026, 3:40 p.m.