Triple
T650926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashi script |
E11343
|
entity |
| Predicate | glyphStyle |
P1851
|
FINISHED |
| Object | semi-cursive letterforms |
—
|
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: semi-cursive letterforms | Statement: [Rashi script, glyphStyle, semi-cursive letterforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glyphStyle Context triple: [Rashi script, glyphStyle, semi-cursive letterforms]
-
A.
symbolicStyle
Indicates that one entity employs or is characterized by a particular symbolic or emblematic style defined by the other entity.
-
B.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
C.
marginStyle
Indicates how the margins around an element are styled or configured in relation to surrounding content.
-
D.
artisticStyle
chosen
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
E.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
- 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_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. |
Created at: March 1, 2026, 7:36 p.m.