Triple
T36444201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 49:2 |
E897822
|
entity |
| Predicate | honorificFocus |
P185509
|
FINISHED |
| Object | status of the Prophet Muhammad |
—
|
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: status of the Prophet Muhammad | Statement: [Quran 49:2, honorificFocus, status of the Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificFocus Context triple: [Quran 49:2, honorificFocus, status of the Prophet Muhammad]
-
A.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
B.
honorificContext
Indicates that one entity is referred to or addressed using an honorific form or within a socially respectful linguistic context relative to another entity or situation.
-
C.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
honorificFunction
Indicates that one entity serves as an honorific title, role, or form of address used in reference to another entity.
- F. None of above. chosen
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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.