Triple
T2236291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katia Mann |
E49287
|
entity |
| Predicate | reasonForEmigration |
P15406
|
FINISHED |
| Object | persecution by the Nazi regime |
—
|
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: persecution by the Nazi regime | Statement: [Katia Mann, reasonForEmigration, persecution by the Nazi regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEmigration Context triple: [Katia Mann, reasonForEmigration, persecution by the Nazi regime]
-
A.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
B.
causeOfExile
chosen
Indicates the reason or circumstance that led to an entity’s exile.
-
C.
reasonForLeaving
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
D.
usedToRestrictEmigrationFrom
Indicates that something was employed as a means to limit or control people leaving a particular place or country.
-
E.
yearOfEmigration
Indicates the specific year in which an entity permanently left its country or place of origin to settle elsewhere.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.