Triple
T26418966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Pfyffer von Altishofen |
E664178
|
entity |
| Predicate | memorialProject |
P501
|
FINISHED |
| Object | Lion Monument |
—
|
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: Lion Monument | Statement: [Karl Pfyffer von Altishofen, memorialProject, Lion Monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialProject Context triple: [Karl Pfyffer von Altishofen, memorialProject, Lion Monument]
-
A.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another entity.
-
B.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
-
C.
hasMemorial
chosen
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
D.
memorialScope
Indicates the extent or boundaries of what is commemorated or covered by a memorial.
-
E.
memorialSiteFor
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 11:42 p.m.