Triple
T26467476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudhayl |
E665805
|
entity |
| Predicate | hasTribalAncestor |
P181394
|
FINISHED |
| Object | Hudhayl ibn Madraka |
—
|
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: Hudhayl ibn Madraka | Statement: [Hudhayl, hasTribalAncestor, Hudhayl ibn Madraka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalAncestor Context triple: [Hudhayl, hasTribalAncestor, Hudhayl ibn Madraka]
-
A.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
B.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
D.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
E.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
- F. None of above. chosen
Provenance (4 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:17 a.m.