Triple
T14733853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Shmuel HaLevi Wosner |
E346147
|
entity |
| Predicate | wroteOnTopic |
P14097
|
FINISHED |
| Object | kashrut |
—
|
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: kashrut | Statement: [Rabbi Shmuel HaLevi Wosner, wroteOnTopic, kashrut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteOnTopic Context triple: [Rabbi Shmuel HaLevi Wosner, wroteOnTopic, kashrut]
-
A.
hasWrittenAbout
chosen
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
B.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
C.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
D.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
E.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec72ea9348190817efcdaa973d7f7 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.