Triple
T11609161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | amaGcaleka |
E275337
|
entity |
| Predicate | followsKinshipSystem |
P81502
|
FINISHED |
| Object | patrilineal |
—
|
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: patrilineal | Statement: [amaGcaleka, followsKinshipSystem, patrilineal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsKinshipSystem Context triple: [amaGcaleka, followsKinshipSystem, patrilineal]
-
A.
usesKinshipSystem
chosen
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
B.
kinshipNetwork
Indicates a familial relationship structure connecting individuals through blood, marriage, or adoption within a broader family network.
-
C.
followsSystem
Indicates that one entity adheres to, complies with, or operates according to a particular system, framework, or set of rules defined by another entity.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
followsPolityOf
Indicates that one entity adopts, adheres to, or operates under the political system, governance model, or policy framework established by 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04231d08190b8a07cd977d11ffa |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.