Triple
T4533410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuru dynasty |
E106349
|
entity |
| Predicate | familyTreeFocus |
P36142
|
FINISHED |
| Object | descendants of King Kuru |
—
|
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: descendants of King Kuru | Statement: [Kuru dynasty, familyTreeFocus, descendants of King Kuru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyTreeFocus Context triple: [Kuru dynasty, familyTreeFocus, descendants of King Kuru]
-
A.
genealogicalLine
chosen
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
genealogicalFunction
Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
-
C.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57a08ec4819091b84d53d7b564a7 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.