Triple
T31802281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zubayrid regime |
E811772
|
entity |
| Predicate | basedOnLineageClaim |
P4867
|
FINISHED |
| Object | Quraysh |
—
|
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: Quraysh | Statement: [Zubayrid regime, basedOnLineageClaim, Quraysh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnLineageClaim Context triple: [Zubayrid regime, basedOnLineageClaim, Quraysh]
-
A.
lineageClaim
chosen
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
B.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
C.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
D.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
E.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 30, 2026, 11:42 p.m.