Triple
T22025599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali ibn Musa |
E543952
|
entity |
| Predicate | relationToAl-Ma'mun |
P17619
|
FINISHED |
| Object | crown prince and designated successor |
—
|
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: crown prince and designated successor | Statement: [Ali ibn Musa, relationToAl-Ma'mun, crown prince and designated successor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToAl-Ma'mun Context triple: [Ali ibn Musa, relationToAl-Ma'mun, crown prince and designated successor]
-
A.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
B.
relationToUthman
Indicates the type of relationship or connection an entity has to Uthman.
-
C.
associatedCaliph
chosen
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
D.
servedCaliph
Indicates that one entity acted in service to, or under the authority of, a caliph.
-
E.
المالك
Indicates a relationship where one entity is the owner or possessor of another entity.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cba61c8190a48ec2c1ee1315b0 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.