Triple
T5901746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georg Elser |
E131241
|
entity |
| Predicate | recognizedPosthumouslyAs |
P58157
|
FINISHED |
| Object | resistance hero |
—
|
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: resistance hero | Statement: [Georg Elser, recognizedPosthumouslyAs, resistance hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedPosthumouslyAs Context triple: [Georg Elser, recognizedPosthumouslyAs, resistance hero]
-
A.
isPosthumousWorkOf
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
B.
isPosthumousAwardRecipientOf
Indicates that an entity received an award that was granted after their death.
-
C.
alsoHonoredAs
chosen
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
D.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
E.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.