Triple
T29432420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makhzum ibn Yaqaza |
E746469
|
entity |
| Predicate | partOfGenealogy |
P77019
|
FINISHED |
| Object | Quraysh tribal lineage |
—
|
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: Quraysh tribal lineage | Statement: [Makhzum ibn Yaqaza, partOfGenealogy, Quraysh tribal lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfGenealogy Context triple: [Makhzum ibn Yaqaza, partOfGenealogy, Quraysh tribal lineage]
-
A.
hasGenealogy
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
-
B.
genealogicalFunction
Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
-
C.
hasGenealogicalSignificance
Indicates that something holds importance or relevance within a genealogical or family-lineage context.
-
D.
genealogicalClassification
chosen
Indicates a relationship where one entity is categorized within a family or lineage structure relative to another, based on genealogical or ancestral connections.
-
E.
genealogicalDescription
Indicates a textual description that explains the genealogical relationships or lineage connections among entities.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 28, 2026, 3:14 p.m.