Triple
T8006533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miao people |
E186375
|
entity |
| Predicate | traditionalMarriageCustom |
P38203
|
FINISHED |
| Object | bridewealth |
—
|
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 | Statement: [Miao people, traditionalMarriageCustom, bridewealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMarriageCustom Context triple: [Miao people, traditionalMarriageCustom, bridewealth]
-
A.
marriageCustom
chosen
Indicates a culturally recognized set of practices, rules, or traditions that govern how marriages are formed, conducted, or maintained between individuals or groups.
-
B.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
C.
marriagePattern
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.
-
D.
marriageContext
Indicates the situational or cultural circumstances under which a marriage occurs or exists, such as legal, social, or religious conditions surrounding the marital relationship.
-
E.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf8a6048190970685a83fd2f59d |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.