Triple
T33447886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messenger of Allah |
E856555
|
entity |
| Predicate | perceivedByCriticsAs |
P60346
|
FINISHED |
| Object | heterodox religious claim |
—
|
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: heterodox religious claim | Statement: [Messenger of Allah, perceivedByCriticsAs, heterodox religious claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedByCriticsAs Context triple: [Messenger of Allah, perceivedByCriticsAs, heterodox religious claim]
-
A.
alsoCalledByCritics
Indicates that critics refer to the same entity by an alternative name or label.
-
B.
isNotedByCriticsFor
chosen
Indicates that something has been recognized and highlighted by critics specifically for a particular quality, feature, or aspect.
-
C.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
D.
typeOfCriticism
Indicates that one entity is a specific kind or category of criticism directed at another entity or subject.
-
E.
criticRole
Indicates that an entity serves in the capacity or function of a critic in relation to another entity or work.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:37 a.m.