Triple
T27623093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umm al-Fadl bint al-Ma'mun |
E696129
|
entity |
| Predicate | caliphalFamilyMember |
P162769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Umm al-Fadl bint al-Ma'mun, caliphalFamilyMember, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caliphalFamilyMember Context triple: [Umm al-Fadl bint al-Ma'mun, caliphalFamilyMember, yes]
-
A.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
B.
caliphalLineage
Indicates a genealogical or dynastic relationship in which one entity descends from, or belongs to, a recognized line of caliphs.
-
C.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
D.
servedCaliph
Indicates that one entity acted in service to, or under the authority of, a caliph.
-
E.
caliphalOrder
Indicates that an action or state occurs by decree, command, or authoritative directive of a caliph.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f630de07c48190b18cffe15ac20618 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:16 p.m.