Triple
T35537173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max und Moritz |
E1026960
|
entity |
| Predicate | endOfStory |
P21330
|
FINISHED |
| Object | Max and Moritz are ground in a mill |
—
|
LITERAL 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: Max and Moritz are ground in a mill | Statement: [Max und Moritz, endOfStory, Max and Moritz are ground in a mill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfStory Context triple: [Max und Moritz, endOfStory, Max and Moritz are ground in a mill]
-
A.
narrativeEnd
chosen
Indicates the point or event at which a narrative, story, or discourse concludes or is brought to an end.
-
B.
concludesStoryOf
Indicates that one entity brings the narrative or storyline of another entity to an end.
-
C.
endOfKingdom
Indicates the point or event at which a kingdom’s rule, existence, or sovereignty comes to a conclusion.
-
D.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
E.
endOfEpisodeOutcome
Indicates the result or consequence that occurs at the conclusion of an episode or event sequence.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:04 p.m.