Triple
T2741294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankunytjatjara |
E60754
|
entity |
| Predicate | hasKinshipSystemType |
P10690
|
FINISHED |
| Object | Western Desert kinship 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: Western Desert kinship system | Statement: [Yankunytjatjara, hasKinshipSystemType, Western Desert kinship system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKinshipSystemType Context triple: [Yankunytjatjara, hasKinshipSystemType, Western Desert kinship system]
-
A.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
C.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
-
E.
hasBloodTypeSystem
Indicates that an entity uses or is classified according to a particular blood type classification system (e.g., ABO, Rh).
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb2f210881909126307cc92ebfef |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.