Triple
T10166234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maaser |
E235209
|
entity |
| Predicate | legalStatusInDiaspora |
P92185
|
FINISHED |
| Object | rabbinic obligation or custom |
—
|
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: rabbinic obligation or custom | Statement: [Maaser, legalStatusInDiaspora, rabbinic obligation or custom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInDiaspora Context triple: [Maaser, legalStatusInDiaspora, rabbinic obligation or custom]
-
A.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
B.
hasRefugeeStatusRecognizedBy
Indicates that an entity’s refugee status has been formally recognized or granted by a specified authority or organization.
-
C.
legalStatusAtArrival
Indicates the legal status or classification an entity held at the time it first arrived at a particular place or jurisdiction.
-
D.
dualCitizenshipStatus
Indicates that an entity holds legal citizenship in two different countries simultaneously.
-
E.
legalStatusOfAmnesty
Indicates the legal status or validity of an amnesty measure granted in relation to an action or entity.
- F. None of above. chosen
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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.