Triple
T20169663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabel Bayrakdarian |
E491923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian-Canadian person |
C18629
|
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: Armenian-Canadian person Context triple: [Isabel Bayrakdarian, instanceOf, Armenian-Canadian person]
-
A.
Armenian-American person
An Armenian-American person is an individual of Armenian heritage who lives in, identifies with, or holds citizenship in the United States, often blending Armenian cultural traditions with American social and cultural practices.
-
B.
Armenian person
chosen
An Armenian person is an individual who identifies with the Armenian nation, typically sharing its historical heritage, cultural traditions, and often the Armenian language, whether living in Armenia or in the global diaspora.
-
C.
Ottoman-Armenian person
An Ottoman-Armenian person is an individual of Armenian ethnic origin who lived in or held citizenship of the Ottoman Empire, shaped by its multicultural, multilingual, and often politically turbulent context.
-
D.
Canadian of Middle Eastern descent
A Canadian of Middle Eastern descent is an individual who holds Canadian identity or citizenship and traces their ancestral or cultural roots to one or more countries in the Middle East.
-
E.
Soviet Armenian person
A Soviet Armenian person is an individual of Armenian ethnicity who lived in or was a citizen of the Armenian Soviet Socialist Republic or the broader Soviet Union during its existence from 1922 to 1991.
- F. None of above.
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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:35 p.m.