Triple
T16610542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Indians |
E403554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Asian ethnic group |
C38113
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: South Asian ethnic group Context triple: [Anglo-Indians, instanceOf, South Asian ethnic group]
-
A.
Indo-Aryan people
Indo-Aryan people are a diverse group of ethnolinguistic communities in South Asia who speak Indo-Aryan languages, a major branch of the Indo-European language family, and share related historical and cultural roots.
-
B.
South Asian family
A South Asian family is a multigenerational, kinship-centered social unit typically characterized by strong interdependence, respect for elders, shared cultural and religious practices, and close ties with extended relatives.
-
C.
South Asian country
A South Asian country is a sovereign nation located in the southern region of Asia, typically characterized by shared historical ties, cultural diversity, and membership in the South Asian regional grouping (such as SAARC).
-
D.
Indian-American
An Indian-American is a person of Indian origin who lives in or is a citizen of the United States, often blending elements of Indian and American cultures in their identity and daily life.
-
E.
Indian American ethnic enclave
An Indian American ethnic enclave is a geographically concentrated neighborhood where Indian immigrants and their descendants live, work, and socialize, maintaining cultural practices, businesses, and institutions that reflect their heritage while interacting with the broader American society.
- F. None of above. chosen
Provenance (1 batch)
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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.