Triple
T34572434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tosafot Yom Tov |
E887659
|
entity |
| Predicate | primaryWorkOn |
P106920
|
FINISHED |
| Object | Mishnah |
E8388
|
NE 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: Mishnah | Statement: [Tosafot Yom Tov, primaryWorkOn, Mishnah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWorkOn Context triple: [Tosafot Yom Tov, primaryWorkOn, Mishnah]
-
A.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
primaryTask
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
D.
workedPrimarilyOn
chosen
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
-
E.
firstWork
Indicates that the related work is the earliest or initial work created, published, or produced by the entity in question.
- F. None of above.
Provenance (4 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37362241c881908c4ec137df071952 |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.