Triple
T25410863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinana tribe |
E636690
|
entity |
| Predicate | roleInArabGenealogies |
P171727
|
FINISHED |
| Object | progenitor tribe of Quraysh |
—
|
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: progenitor tribe of Quraysh | Statement: [Kinana tribe, roleInArabGenealogies, progenitor tribe of Quraysh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInArabGenealogies Context triple: [Kinana tribe, roleInArabGenealogies, progenitor tribe of Quraysh]
-
A.
roleInArabia
Indicates that an entity holds or held a specific role, position, or function within the context of Arabia.
-
B.
roleInArabStrap
Indicates that an entity holds or held a specific role or position within the band Arab Strap.
-
C.
roleAtKarbala
Indicates the specific role, position, or function an entity held in relation to the events of the Battle of Karbala.
-
D.
fatherInArabic
Indicates that one entity is the word used for "father" in the Arabic language corresponding to the other entity.
-
E.
caliphalFamilyMember
Indicates that one entity is a member of a caliphal family, i.e., related by blood or lineage to a caliph or ruling caliphal dynasty.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 21, 2026, 1:53 p.m.