Triple

T18340691
Position Surface form Disambiguated ID Type / Status
Subject Pim Fortuyn E439392 entity
Predicate givenName P17 FINISHED
Object Petrus 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: Petrus | Statement: [Pim Fortuyn, givenName, Petrus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Petrus
Context triple: [Pim Fortuyn, givenName, Petrus]
  • A. Petrus chosen
    Petrus is the Latin form of the name Peter, historically used in religious and classical contexts and serving as the root for various European given names.
  • B. Pollachius
    Pollachius is a genus of marine fish in the cod family that includes commercially important species commonly known as pollock.
  • C. Lambertus
    Lambertus is a Latinized given name historically used in European contexts, particularly in religious and scholarly settings.
  • D. Svatý Petr
    Svatý Petr is a popular mountain area and ski resort sector of Špindlerův Mlýn in the Krkonoše (Giant) Mountains of the Czech Republic.
  • E. Norbertus
    Norbertus is a Latinized form of the given name Norbert, historically used in ecclesiastical and scholarly contexts.
  • 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_69d8b9175fec8190af865699b4e64d8c completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50ed146fc819092b08cb91defb03b completed April 19, 2026, 5:20 p.m.
Created at: April 10, 2026, 10:37 a.m.