Triple
T6237715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsi community in Gujarat |
E139516
|
entity |
| Predicate | diasporicOrigin |
P194
|
FINISHED |
| Object | migrants from Greater Iran |
—
|
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: migrants from Greater Iran | Statement: [Parsi community in Gujarat, diasporicOrigin, migrants from Greater Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporicOrigin Context triple: [Parsi community in Gujarat, diasporicOrigin, migrants from Greater Iran]
-
A.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
diasporaCharacteristic
Indicates that an entity possesses a quality, feature, or attribute specifically associated with a diaspora community or condition.
-
C.
diasporaType
Indicates the specific kind or category of diaspora relationship that exists between a group and its place of origin.
-
D.
countryOfDiaspora
Indicates the country in which a diaspora community originating from another place is located.
-
E.
diasporaComponentOf
Indicates that one entity is a constituent or subgroup of the broader diaspora associated with another entity.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0630373088190a9d4b1f7e442c129 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.