Triple
T4769052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravad version of Sefer Yetzirah |
E105880
|
entity |
| Predicate | hasAuthorialRole |
P27764
|
FINISHED |
| Object | Ravad as commentator |
—
|
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: Ravad as commentator | Statement: [Ravad version of Sefer Yetzirah, hasAuthorialRole, Ravad as commentator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialRole Context triple: [Ravad version of Sefer Yetzirah, hasAuthorialRole, Ravad as commentator]
-
A.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
hasAuthorType
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
D.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
E.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.