Triple
T36528013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht am Morgarten |
E900358
|
entity |
| Predicate | wirdErinnertDurch |
P65341
|
FINISHED |
| Object | Morgarten-Denkmal |
—
|
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: Morgarten-Denkmal | Statement: [Schlacht am Morgarten, wirdErinnertDurch, Morgarten-Denkmal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirdErinnertDurch Context triple: [Schlacht am Morgarten, wirdErinnertDurch, Morgarten-Denkmal]
-
A.
rememberedThrough
chosen
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
B.
recalledBy
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
C.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
D.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
E.
retainsMemoriesOf
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.