Triple
T615681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Jews |
E12197
|
entity |
| Predicate | diasporaLanguageShift |
P4292
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Persian Jews, diasporaLanguageShift, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporaLanguageShift Context triple: [Persian Jews, diasporaLanguageShift, English]
-
A.
heritageLanguageShift
Indicates a change over time in which a community or individual moves away from using their ancestral or heritage language toward another dominant language.
-
B.
languageShift
chosen
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
C.
languageDiversity
Indicates the degree to which multiple distinct languages are present and used within a given context or population.
-
D.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
E.
hasDiaspora
Indicates that a group, community, or population has members who have dispersed or settled outside their original homeland or region.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.