Triple
T1583823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fipa people |
E34025
|
entity |
| Predicate | marriageSystem |
P11275
|
FINISHED |
| Object | bridewealth practices |
—
|
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: bridewealth practices | Statement: [Fipa people, marriageSystem, bridewealth practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageSystem Context triple: [Fipa people, marriageSystem, bridewealth practices]
-
A.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
marriagePattern
chosen
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
-
C.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
-
D.
maritalBasis
Indicates that the relationship or status in question is founded on, justified by, or determined due to a marital relationship between the involved entities.
-
E.
marriageCharacterization
Indicates how a marriage is described, evaluated, or characterized in terms of its qualities, dynamics, or nature.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.