Triple
T36344681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mustafa |
E895028
|
entity |
| Predicate | hasReligiousTitleForm |
P146129
|
FINISHED |
| Object | Al-Mustafa |
E895028
|
NE 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: Al-Mustafa | Statement: [Mustafa, hasReligiousTitleForm, Al-Mustafa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousTitleForm Context triple: [Mustafa, hasReligiousTitleForm, Al-Mustafa]
-
A.
hasReligiousName
chosen
Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
-
B.
ecclesiasticalTitleIncludes
Indicates that one ecclesiastical title contains, subsumes, or incorporates another ecclesiastical title as part of its designation or scope.
-
C.
isEcclesiasticalTitle
Indicates that the entity functions as a formal religious or church office, rank, or honorific title within an ecclesiastical context.
-
D.
hasReligiousForms
Indicates that an entity possesses or is associated with specific religious expressions, practices, or organizational structures.
-
E.
hasSecularTitle
Indicates that an entity holds or is associated with a non-religious, civil, or lay title or designation.
- F. None of above.
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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfbb966c8190ab9a83f79964d691 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.