Triple
T35296587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dewa |
E1019385
|
entity |
| Predicate | hasReligiousTitleInName |
P502
|
FINISHED |
| Object | Sharif |
E342419
|
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: Sharif | Statement: [Dewa, hasReligiousTitleInName, Sharif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousTitleInName Context triple: [Dewa, hasReligiousTitleInName, Sharif]
-
A.
hasReligiousName
Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
-
B.
hasReligiousAffiliationInName
Indicates that an entity’s name explicitly includes or reflects a religious affiliation or association.
-
C.
religiousTitle
chosen
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
-
D.
ecclesiasticalTitleIncludes
Indicates that one ecclesiastical title contains, subsumes, or incorporates another ecclesiastical title as part of its designation or scope.
-
E.
isEcclesiasticalTitle
Indicates that the entity functions as a formal religious or church office, rank, or honorific title within an ecclesiastical context.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819e5b9608190a9e0e230cc8e05d6 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.