Triple
T28729051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banias |
E730304
|
entity |
| Predicate | endogamy |
P11275
|
FINISHED |
| Object | largely endogamous 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 community | Statement: [Banias, endogamy, largely endogamous community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endogamy Context triple: [Banias, endogamy, largely endogamous community]
-
A.
monogamy
Indicates an exclusive romantic or sexual relationship in which an individual has only one partner at a time.
-
B.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
C.
forcedMarriage
Indicates that one entity compels another into a marital union without their free and informed consent.
-
D.
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.
-
E.
patrilocal
Indicates that, after marriage, a couple resides with or near the husband's family or kin group.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657662cec8190b1cf4ec832658a3b |
completed | May 2, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:57 a.m.