Triple
T30704884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İstemi Yabghu |
E781723
|
entity |
| Predicate | siblingOrRelativeType |
P94755
|
FINISHED |
| Object | brother-in-law of Bumin Qaghan |
—
|
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: brother-in-law of Bumin Qaghan | Statement: [İstemi Yabghu, siblingOrRelativeType, brother-in-law of Bumin Qaghan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingOrRelativeType Context triple: [İstemi Yabghu, siblingOrRelativeType, brother-in-law of Bumin Qaghan]
-
A.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
B.
relationshipToRelative
chosen
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
D.
nieceOrNephewOf
Indicates that one person is the niece or nephew (the child of a sibling or sibling-in-law) of another person.
-
E.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c191778819093c79b1b785fbc39 |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:35 p.m.