Triple
T28278956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mudar |
E713086
|
entity |
| Predicate | positionInArabGenealogy |
P171727
|
FINISHED |
| Object | major ancestral tribal grouping |
—
|
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: major ancestral tribal grouping | Statement: [Mudar, positionInArabGenealogy, major ancestral tribal grouping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInArabGenealogy Context triple: [Mudar, positionInArabGenealogy, major ancestral tribal grouping]
-
A.
roleInArabGenealogies
chosen
Indicates the role or position an entity holds within traditional Arab genealogical lineages or family trees.
-
B.
familyTreeLocation
Indicates the position or role an individual occupies within a family tree relative to other family members.
-
C.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
D.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
E.
positionOnKaaba
Indicates that one entity occupies a specific location or placement on the surface or structure of the Kaaba.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 11:21 p.m.