Triple
T15804288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musaf of Shabbat |
E383171
|
entity |
| Predicate | languageTypicallyUsed |
P42338
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Musaf of Shabbat, languageTypicallyUsed, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageTypicallyUsed Context triple: [Musaf of Shabbat, languageTypicallyUsed, Hebrew]
-
A.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
B.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
C.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
D.
typicalLanguages
chosen
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b525b1c08190acffab06d89dbdbe |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.