Triple
T15623649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assef |
E375625
|
entity |
| Predicate | religiousIdentityInFiction |
P83945
|
FINISHED |
| Object | Sunni Muslim |
—
|
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: Sunni Muslim | Statement: [Assef, religiousIdentityInFiction, Sunni Muslim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousIdentityInFiction Context triple: [Assef, religiousIdentityInFiction, Sunni Muslim]
-
A.
religionOfCharacterPortrayed
chosen
Indicates that a work portrays a character as adhering to or being associated with a particular religion.
-
B.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
livesInFiction
Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
religiousCharacteristic
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9cfd94819091459aa17a002eaf |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.