Triple
T23955925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhetri |
E603786
|
entity |
| Predicate | followsKinshipRule |
P81502
|
FINISHED |
| Object | patrilineal descent |
—
|
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: patrilineal descent | Statement: [Chhetri, followsKinshipRule, patrilineal descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsKinshipRule Context triple: [Chhetri, followsKinshipRule, patrilineal descent]
-
A.
usesKinshipSystem
chosen
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
followsSonOf
Indicates that one entity follows another entity who is the son of a specified person or entity.
-
D.
followsByDefinition
Indicates that one concept, statement, or item logically or definitionally comes immediately after another as a direct consequence of how the terms are defined.
-
E.
followsGenerationsOf
Indicates that one entity comes after and is separated from another by multiple generations in a lineage or succession.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d6d7688190bedf55dda8e72b2b |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.