Triple
T38642825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rema on Shulchan Aruch |
E938644
|
entity |
| Predicate | integratesCustomsOf |
P176448
|
FINISHED |
| Object | Central European Jewry |
—
|
NE NERFINISHED |
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: Central European Jewry | Statement: [Rema on Shulchan Aruch, integratesCustomsOf, Central European Jewry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesCustomsOf Context triple: [Rema on Shulchan Aruch, integratesCustomsOf, Central European Jewry]
-
A.
customs
Indicates that an entity is responsible for regulating, inspecting, or processing goods and people as they cross a border for legal and tax purposes.
-
B.
shareCustomsRegime
Indicates that two or more entities are subject to, or operate under, the same customs regime or set of customs regulations.
-
C.
customsAssociated
Indicates that certain cultural or social customs are connected with, practiced by, or characteristic of a particular entity.
-
D.
customsStyle
chosen
Indicates that one entity follows, represents, or is characterized by the customs or stylistic traditions associated with another entity.
-
E.
honorCustom
Indicates that one entity respects, observes, or upholds the traditions, practices, or norms associated with another entity’s custom.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.