Triple
T19990408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karel Reisz |
E494045
|
entity |
| Predicate | wasRefugeeFrom |
P47614
|
FINISHED |
| Object | Nazi-occupied Czechoslovakia |
—
|
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: Nazi-occupied Czechoslovakia | Statement: [Karel Reisz, wasRefugeeFrom, Nazi-occupied Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRefugeeFrom Context triple: [Karel Reisz, wasRefugeeFrom, Nazi-occupied Czechoslovakia]
-
A.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
B.
originalRefugeeOrigin
chosen
Indicates the place or country from which a refugee initially fled or was displaced.
-
C.
receivedAsylumFrom
Indicates that one entity was granted asylum or refuge by another entity, typically a state or institution.
-
D.
soughtAsylumAt
Indicates that an individual or group applied for protection or refuge at a particular country, institution, or authority.
-
E.
refugeeOriginEvent
Indicates an event or circumstance that caused or is associated with a person or group becoming refugees and leaving their place of origin.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdecf108190a5b215fd25bc4dda |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:30 p.m.