Triple
T24135242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Yeshiva |
E598063
|
entity |
| Predicate | survivalRoute |
P139934
|
FINISHED |
| Object | escape via Japan to Shanghai during World War II |
—
|
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: escape via Japan to Shanghai during World War II | Statement: [Mir Yeshiva, survivalRoute, escape via Japan to Shanghai during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalRoute Context triple: [Mir Yeshiva, survivalRoute, escape via Japan to Shanghai during World War II]
-
A.
survivorsJourney
Indicates the ongoing process or path a survivor takes as they cope with, adapt to, and move forward from a traumatic or life-threatening experience.
-
B.
survivalTheme
chosen
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
-
E.
survivingUse
Indicates that one entity continues to make use of another entity or resource after an event that could have ended or invalidated that use.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7c3ce08190bcbd9056a6630c2f |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.