Triple
T34698935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyangatom people |
E1000306
|
entity |
| Predicate | genderRolePattern |
P69451
|
FINISHED |
| Object | patriarchal |
—
|
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: patriarchal | Statement: [Nyangatom people, genderRolePattern, patriarchal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderRolePattern Context triple: [Nyangatom people, genderRolePattern, patriarchal]
-
A.
genderRoleAssociation
Indicates an association between a gender and a particular social role, behavior, or expectation.
-
B.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
C.
genderRoleSignificance
Indicates the extent to which gender roles are considered important, influential, or defining within a given relationship, context, or interaction.
-
D.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
E.
hasGenderRole
chosen
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.