Triple
T24241737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zürich Nordheim cemetery |
E603245
|
entity |
| Predicate | isPlaceOfMemorial |
P115845
|
FINISHED |
| Object | Udo Jürgens memorial |
—
|
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: Udo Jürgens memorial | Statement: [Zürich Nordheim cemetery, isPlaceOfMemorial, Udo Jürgens memorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlaceOfMemorial Context triple: [Zürich Nordheim cemetery, isPlaceOfMemorial, Udo Jürgens memorial]
-
A.
memorialLocatedAt
Indicates that a memorial is situated or found at a specific location.
-
B.
memorialSiteFor
chosen
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
C.
isNationalMemorialOf
Indicates that a site, structure, or monument has been officially designated as a national memorial commemorating or representing a particular entity, event, or subject.
-
D.
numberCommemoratedOnMemorial
Indicates the quantity of individuals or entities that are honored or remembered on a particular memorial.
-
E.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
- F. None of above.
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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa04fe08190922d6abde695571a |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.