Triple
T13762107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sholem Secunda |
E330636
|
entity |
| Predicate | hasWorkInLanguage |
P45484
|
FINISHED |
| Object | Yiddish |
—
|
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: Yiddish | Statement: [Sholem Secunda, hasWorkInLanguage, Yiddish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInLanguage Context triple: [Sholem Secunda, hasWorkInLanguage, Yiddish]
-
A.
hasWorkedInLanguage
chosen
Indicates that an entity has performed work or professional activities using a particular language.
-
B.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
C.
hasWorkTranslatedInto
Indicates that a work has been translated into a specified language or target work.
-
D.
hasWorkedOnLanguageFamily
Indicates that an entity (such as a person or organization) has conducted work, research, or professional activity related to a particular language family.
-
E.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02250f4881908d5193b3d5d25844 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.