Triple
T36957483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die, Führer, Die! |
E914223
|
entity |
| Predicate | hasEndSequence |
P191352
|
FINISHED |
| Object | victory screen after defeating Hitler |
—
|
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: victory screen after defeating Hitler | Statement: [Die, Führer, Die!, hasEndSequence, victory screen after defeating Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndSequence Context triple: [Die, Führer, Die!, hasEndSequence, victory screen after defeating Hitler]
-
A.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
B.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
C.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
D.
hasCharacterSequence
chosen
Indicates that one entity contains, exhibits, or follows a specific ordered sequence of characters.
-
E.
hasLimitingSequence
Indicates that one entity serves as a limiting sequence (in the sense of convergence or approximation) for another 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:13 p.m.