Triple
T34288536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hūr |
E879811
|
entity |
| Predicate | notableExegesisBy |
P22732
|
FINISHED |
| Object | al-Ṭabarī |
E102963
|
NE 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: al-Ṭabarī | Statement: [Hūr, notableExegesisBy, al-Ṭabarī]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExegesisBy Context triple: [Hūr, notableExegesisBy, al-Ṭabarī]
-
A.
notableInterpretationBy
chosen
Indicates that an entity has a significant or widely recognized interpretation, analysis, or reading provided by a particular agent (such as a person, group, or source).
-
B.
notableWorkDiscussed
Indicates that a particular work (such as a book, film, or artwork) is the subject of discussion, analysis, or commentary in relation to another entity.
-
C.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
D.
notableInterpretation
Indicates that an entity is a significant or widely recognized interpretation, rendition, or version of another work, concept, or subject.
-
E.
notableAuthorMention
Indicates that a notable or well-known author is referenced or cited in relation to the subject.
- F. None of above.
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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e631eb688190a9bc2fd755bcfc2e |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.