Triple
T33236265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maithil community |
E850835
|
entity |
| Predicate | dowryPractice |
P26744
|
FINISHED |
| Object | historically prevalent |
—
|
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: historically prevalent | Statement: [Maithil community, dowryPractice, historically prevalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dowryPractice Context triple: [Maithil community, dowryPractice, historically prevalent]
-
A.
dowry
chosen
Indicates the transfer of wealth or property from a bride’s family to the groom or his family as part of a marriage arrangement.
-
B.
broughtAsDowryTo
Indicates that one entity was transferred as dowry to another entity, typically as part of a marriage arrangement.
-
C.
arrangedMarriageFor
Indicates that one entity has organized or set up a marriage for another entity.
-
D.
forcedMarriage
Indicates that one entity compels another into a marital union without their free and informed consent.
-
E.
bride
Indicates that an entity is a woman who is getting married or has just been married in relation to a wedding event or spouse.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.