Triple
T37260010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swazi royal family |
E924232
|
entity |
| Predicate | memberOfEthnicDynasties |
P100586
|
FINISHED |
| Object | Bantu royal houses |
—
|
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: Bantu royal houses | Statement: [Swazi royal family, memberOfEthnicDynasties, Bantu royal houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfEthnicDynasties Context triple: [Swazi royal family, memberOfEthnicDynasties, Bantu royal houses]
-
A.
dynasticEthnicity
chosen
Indicates the ethnic or cultural lineage associated with a particular dynasty or ruling house.
-
B.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
roleWithinEthnicGroup
Indicates the specific social, cultural, or functional position an entity holds within a particular ethnic group.
-
E.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:15 p.m.