Triple
T36991311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmaBhaca |
E915105
|
entity |
| Predicate | usesPatrilinealDescent |
P182263
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AmaBhaca, usesPatrilinealDescent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPatrilinealDescent Context triple: [AmaBhaca, usesPatrilinealDescent, yes]
-
A.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
B.
viewOnPatrilinealDescent
chosen
Indicates a stance, belief, or interpretation regarding the principle or practice of tracing descent and inheritance through the male (father’s) lineage.
-
C.
patriarchalLineage
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
D.
usedMatrilinealIdentity
Indicates that an entity adopts or applies identity, status, or affiliation traced specifically through the maternal (mother’s) lineage.
-
E.
traditionalDescendants
Indicates that one entity is a descendant of another according to traditional or customary lineage or inheritance rules.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:14 p.m.