Triple
T18561096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semendo people |
E453639
|
entity |
| Predicate | kinshipFeature |
P81502
|
FINISHED |
| Object | bilateral kinship elements |
—
|
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: bilateral kinship elements | Statement: [Semendo people, kinshipFeature, bilateral kinship elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kinshipFeature Context triple: [Semendo people, kinshipFeature, bilateral kinship elements]
-
A.
kinshipNetwork
Indicates a familial relationship structure connecting individuals through blood, marriage, or adoption within a broader family network.
-
B.
usesKinshipSystem
chosen
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
C.
kinshipMetaphor
Indicates a figurative or symbolic kinship relationship between entities, where family terms are used metaphorically rather than for literal biological or legal ties.
-
D.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5380a46f08190afe7ca2ddfe209d5 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:42 a.m.