Triple
T14796882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakyiri |
E347803
|
entity |
| Predicate | norms |
P22982
|
FINISHED |
| Object | exogamous marriage rules within Akan society |
—
|
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: exogamous marriage rules within Akan society | Statement: [Asakyiri, norms, exogamous marriage rules within Akan society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: norms Context triple: [Asakyiri, norms, exogamous marriage rules within Akan society]
-
A.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
-
C.
normativelyIncludes
Indicates that one norm or rule encompasses, subsumes, or otherwise includes another within its prescribed scope or requirements.
-
D.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
E.
hasNorm
chosen
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.