Triple
T1252343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kol Nidre |
E26904
|
entity |
| Predicate | historicalLanguageLayer |
P21970
|
FINISHED |
| Object | Aramaic core text |
—
|
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: Aramaic core text | Statement: [Kol Nidre, historicalLanguageLayer, Aramaic core text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageLayer Context triple: [Kol Nidre, historicalLanguageLayer, Aramaic core text]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
C.
historicalLinguistics
Indicates the study of how languages change over time and the relationships between earlier and later language forms.
-
D.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
-
E.
historicalLanguageOfEnvironment
chosen
Indicates that a language was historically used or prevalent in a given environment or setting, even if it is not the current primary language there.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf875cf48190b6781d41097ee39b |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.