Triple
T8209391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongass people |
E191775
|
entity |
| Predicate | usesKinshipSystem |
P81502
|
FINISHED |
| Object | matrilineal clans |
—
|
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: matrilineal clans | Statement: [Tongass people, usesKinshipSystem, matrilineal clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKinshipSystem Context triple: [Tongass people, usesKinshipSystem, matrilineal clans]
-
A.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
associatedWithPatriarch
Indicates that an entity has a relationship, connection, or affiliation with a patriarch, such as being under their authority, influence, or domain.
-
C.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
D.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
E.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
- F. None of above. chosen
Provenance (4 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dc784881908e1f63ac907cdd01 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.