Triple
T32135145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Iranians |
E820747
|
entity |
| Predicate | diasporaCity |
P21972
|
FINISHED |
| Object | Los Angeles |
—
|
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: Los Angeles | Statement: [Christian Iranians, diasporaCity, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporaCity Context triple: [Christian Iranians, diasporaCity, Los Angeles]
-
A.
majorDiasporaCity
chosen
Indicates that a city serves as a primary center or hub for a particular diaspora community outside its place of origin.
-
B.
diasporaType
Indicates the specific kind or category of diaspora relationship that exists between a group and its place of origin.
-
C.
diasporaCenter
Indicates a location or institution that serves as a focal point or hub for a dispersed community living outside its ancestral homeland.
-
D.
diasporaComponentOf
Indicates that one entity is a constituent or subgroup of the broader diaspora associated with another entity.
-
E.
diasporaUse
Indicates that members of a diaspora community use, practice, or engage with something (e.g., a language, custom, or resource) in the context of their life outside 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:30 a.m.