Triple
T37964634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mu'tamid |
E947103
|
entity |
| Predicate | appointedAsHeir |
P100751
|
FINISHED |
| Object | Al-Mufawwid |
—
|
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: Al-Mufawwid | Statement: [Al-Mu'tamid, appointedAsHeir, Al-Mufawwid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsHeir Context triple: [Al-Mu'tamid, appointedAsHeir, Al-Mufawwid]
-
A.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
-
B.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
C.
succeededAsHeir
Indicates that one entity became the heir in place of, or following, another entity, typically upon the latter’s death or abdication.
-
D.
madeHeirBy
chosen
Indicates that one entity is designated or appointed as the heir of another entity.
-
E.
sawAsHeir
Indicates that one entity regarded another as their heir or successor, expecting them to inherit their role, position, or estate.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:20 p.m.