Triple
T21938678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramgarhia |
E541758
|
entity |
| Predicate | endogamyPractice |
P11275
|
FINISHED |
| Object | largely endogamous within community |
—
|
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: largely endogamous within community | Statement: [Ramgarhia, endogamyPractice, largely endogamous within community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endogamyPractice Context triple: [Ramgarhia, endogamyPractice, largely endogamous within community]
-
A.
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.
-
B.
marriageRestriction
Indicates a legal or social limitation on who or under what conditions individuals are allowed to marry.
-
C.
monogamy
Indicates an exclusive romantic or sexual relationship in which an individual has only one partner at a time.
-
D.
maritalPolicy
Indicates a relationship where an authority or institution defines rules, conditions, or norms governing marriage between individuals.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241f582c81909a244419cec38b19 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.