Triple
T16222401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory of Nazianzus family |
E393760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cappadocian family |
C37139
|
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: Cappadocian family Context triple: [Gregory of Nazianzus family, instanceOf, Cappadocian family]
-
A.
member of Cappadocian Christian family
A member of a Cappadocian Christian family is an individual belonging to a household in the Cappadocia region whose identity, daily life, and social relations are shaped by early Christian beliefs, practices, and community traditions.
-
B.
Turkish family
A Turkish family is a close-knit social unit typically characterized by strong intergenerational bonds, respect for elders, and a blend of traditional values with modern Turkish cultural practices.
-
C.
Phanariote family
A Phanariote family is a prominent Greek Orthodox lineage from Constantinople’s Phanar district that gained wealth and political influence under the Ottoman Empire, often supplying high-ranking officials and princes to the Danubian Principalities.
-
D.
Syrian clan
A Syrian clan is an extended kinship group in Syria, often spanning multiple generations and households, bound by shared ancestry, social obligations, and mutual support within a specific tribal, regional, or sectarian context.
-
E.
Egyptian family
An Egyptian family is a close-knit social unit typically comprising multiple generations, where strong kinship ties, respect for elders, and shared cultural and religious traditions shape daily life and responsibilities.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:03 a.m.