Triple
T3727565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkenazi cursive Hebrew |
E81785
|
entity |
| Predicate | hasDistinctFinalForms |
P17610
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ashkenazi cursive Hebrew, hasDistinctFinalForms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctFinalForms Context triple: [Ashkenazi cursive Hebrew, hasDistinctFinalForms, yes]
-
A.
hasDistinctLetterForms
Indicates that the related writing system or symbol set uses different visual shapes or styles for the same letter in different contexts (such as position, case, or usage).
-
B.
hasDistinctVocabulary
Indicates that one entity’s vocabulary is different or distinguishable from that of another entity.
-
C.
hasDistinctGrammar
Indicates that the subject’s grammar system is different in structure or rules from that of the object.
-
D.
hasFinalFormLetters
chosen
Indicates that certain letters in a script change to a distinct "final" shape when they appear at the end of a word.
-
E.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf7a6908190bd0c3bb5c55ab9ee |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.