Triple
T26758172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exilliteratur |
E674724
|
entity |
| Predicate | hatWichtigeExilländer |
P162358
|
FINISHED |
| Object | Sowjetunion |
—
|
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: Sowjetunion | Statement: [Exilliteratur, hatWichtigeExilländer, Sowjetunion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatWichtigeExilländer Context triple: [Exilliteratur, hatWichtigeExilländer, Sowjetunion]
-
A.
hasNotableEmigrant
Indicates that an entity has at least one emigrant who is considered notable or significant in some recognized way.
-
B.
hasSignificantEmigrationTo
Indicates that a substantial number of people leave one place, group, or entity to move and settle in another specific place, group, or entity.
-
C.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
D.
exileCountry
Indicates that an entity has been banished from or forced to live outside a specified country.
-
E.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
- F. None of above. chosen
Provenance (4 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f62473a38481909b919f88ffb5b492 |
completed | May 2, 2026, 4:21 p.m. |
Created at: April 27, 2026, 3:56 a.m.