Triple
T650916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashi script |
E11343
|
entity |
| Predicate | typographicRole |
P17754
|
FINISHED |
| Object | commentary typeface |
—
|
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: commentary typeface | Statement: [Rashi script, typographicRole, commentary typeface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typographicRole Context triple: [Rashi script, typographicRole, commentary typeface]
-
A.
orthographicRole
Indicates the functional role that a written form or spelling plays within an orthographic system (e.g., as a letter, diacritic, punctuation mark, or other script element).
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
textType
Indicates the classification of a text according to its type, format, or genre.
-
E.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
- F. None of above. chosen
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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f33b6d881908b6662b73d6fe833 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.