Triple
T2381675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopi people |
E46323
|
entity |
| Predicate | traditionalDescentSystem |
P23527
|
FINISHED |
| Object | matrilineal |
—
|
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 | Statement: [Hopi people, traditionalDescentSystem, matrilineal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDescentSystem Context triple: [Hopi people, traditionalDescentSystem, matrilineal]
-
A.
descentSystem
chosen
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
B.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
C.
typicalAncestryDescription
Indicates the usual or most common ancestral background associated with an entity.
-
D.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
E.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b98c988190abdb4fe51bf65bde |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.