Triple
T34424413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiddushin |
E883629
|
entity |
| Predicate | relatedTractate |
P205429
|
FINISHED |
| Object | Gittin |
E883628
|
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: Gittin | Statement: [Kiddushin, relatedTractate, Gittin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTractate Context triple: [Kiddushin, relatedTractate, Gittin]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedPaliName
Indicates that one entity has an associated or corresponding name expressed in Pali for the other entity.
-
C.
relatedToDhatu
Indicates a general relationship or association between an entity and a specific dhatu (fundamental element or root concept).
-
D.
relatedStudy
Indicates that one study is connected or relevant to another study, typically through shared topics, methods, or findings.
-
E.
relatedDecree
Indicates that one entity has a decree, order, or formal directive that is connected, associated, or otherwise relevant to another entity.
- F. None of above. chosen
Provenance (5 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370ddc10e88190b6d5e7eb6fb52f01 |
completed | June 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2 a.m.