Triple

T16404263
Position Surface form Disambiguated ID Type / Status
Subject Stevenskerk Nijmegen E398383 entity
Predicate nativeName P15 FINISHED
Object Stevenskerk E408479 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: Stevenskerk | Statement: [Stevenskerk Nijmegen, nativeName, Stevenskerk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stevenskerk
Context triple: [Stevenskerk Nijmegen, nativeName, Stevenskerk]
  • A. Stevenskerk chosen
    Stevenskerk is a historic medieval church in Nijmegen, the Netherlands, known as the city's main and oldest church.
  • B. Westerkerk
    Westerkerk is a prominent 17th-century Protestant church in central Amsterdam, renowned for its tall tower and association with Dutch Golden Age history.
  • C. Munsterkerk
    Munsterkerk is a prominent Romanesque church in Roermond, Netherlands, known for its distinctive twin towers and historical significance.
  • D. St. Maartenskerk
    St. Maartenskerk is a historic church in the Dutch town of Tiel, notable for its medieval architecture and prominent tower.
  • E. St. Janskerk
    St. Janskerk is a prominent Gothic church in Maastricht, Netherlands, known for its striking red tower and historic role in the city’s religious and architectural heritage.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d1f16481909adb19dab86dcc72 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003c6094e481909aa7402fd17fedae completed May 10, 2026, 8:05 a.m.
Created at: April 10, 2026, 5:09 a.m.