Triple
T30119793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Khazraj (pre-Islamic period) |
E765526
|
entity |
| Predicate | sisterTribe |
P71234
|
FINISHED |
| Object | Banu Aws |
—
|
NE NERFINISHED |
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: Banu Aws | Statement: [Banu Khazraj (pre-Islamic period), sisterTribe, Banu Aws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterTribe Context triple: [Banu Khazraj (pre-Islamic period), sisterTribe, Banu Aws]
-
A.
sisterRace
Indicates that two races or species are closely related or derived from a common origin, often treated as parallel or counterpart groups.
-
B.
inTribe
Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
-
C.
hasBrotherTribe
chosen
Indicates a relationship where one tribe is recognized as the brother or closely allied counterpart of another tribe.
-
D.
sisterTeam
Indicates that two teams are closely affiliated or paired, typically within the same organization or structure, as "sister" teams.
-
E.
sisterSettlement
Indicates that two settlements are formally paired or twinned, typically to promote cultural, social, or economic exchange.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dea016c8190b961a805960152bb |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:13 p.m.