Triple
T24991143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinnauri culture |
E625450
|
entity |
| Predicate | hasFamilyStructure |
P152974
|
FINISHED |
| Object | joint family system |
—
|
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: joint family system | Statement: [Kinnauri culture, hasFamilyStructure, joint family system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyStructure Context triple: [Kinnauri culture, hasFamilyStructure, joint family system]
-
A.
hasFamilySituation
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
B.
hasFamilyOrganization
chosen
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
-
C.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
D.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
E.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 6:03 a.m.