Triple
T27044475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abd al-Rahman |
E684583
|
entity |
| Predicate | honorificTheophoricElement |
P54566
|
FINISHED |
| Object | al-Rahman |
—
|
NE NERFINISHED |
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-Rahman | Statement: [Abd al-Rahman, honorificTheophoricElement, al-Rahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificTheophoricElement Context triple: [Abd al-Rahman, honorificTheophoricElement, al-Rahman]
-
A.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
B.
honorificEpitet
Indicates that one entity is referred to or addressed using an honorific epithet, expressing respect, status, or reverence toward that entity.
-
C.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
D.
honorificNameOf
chosen
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
E.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 8:08 a.m.