Triple
T26186214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greatest Master |
E654836
|
entity |
| Predicate | honorificFormOf |
P54566
|
FINISHED |
| Object | al-Shaykh al-Akbar |
—
|
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-Shaykh al-Akbar | Statement: [The Greatest Master, honorificFormOf, al-Shaykh al-Akbar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificFormOf Context triple: [The Greatest Master, honorificFormOf, al-Shaykh al-Akbar]
-
A.
honorificNameOf
chosen
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
B.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
C.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
D.
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.
-
E.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 8:42 p.m.