Triple
T4838970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashbi |
E108131
|
entity |
| Predicate | traditionalRoleInText |
P11527
|
FINISHED |
| Object | protagonist of the Zoharic dialogues |
—
|
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: protagonist of the Zoharic dialogues | Statement: [Rashbi, traditionalRoleInText, protagonist of the Zoharic dialogues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRoleInText Context triple: [Rashbi, traditionalRoleInText, protagonist of the Zoharic dialogues]
-
A.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
traditionalAuthor
Indicates that an entity is regarded as the conventional or historically accepted author of a work, even if actual authorship may be uncertain or disputed.
-
D.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
E.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.