Triple
T26467580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khuzaʿa |
E665809
|
entity |
| Predicate | notableClanOrSection |
P111063
|
FINISHED |
| Object | Banu al-Mustaliq |
—
|
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 al-Mustaliq | Statement: [Khuzaʿa, notableClanOrSection, Banu al-Mustaliq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClanOrSection Context triple: [Khuzaʿa, notableClanOrSection, Banu al-Mustaliq]
-
A.
notableClans
chosen
Indicates that there exists a significant or historically important clan associated with the subject.
-
B.
notableSect
Indicates that an entity is a significant or prominent sect, denomination, or subgroup within a broader religious, ideological, or organizational context.
-
C.
notableClanOrigin
Indicates that an entity is notably associated with originating from, belonging to, or being historically linked to a particular clan.
-
D.
notableSection
Indicates that a particular part or segment of something is especially important, prominent, or worthy of attention within the whole.
-
E.
notableWarriorSociety
Indicates that an entity is recognized as a prominent or historically significant warrior group or martial society.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: April 27, 2026, 12:17 a.m.