Triple
T19723221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donmeh |
E473660
|
entity |
| Predicate | secretPractice |
P137077
|
FINISHED |
| Object | observance of Jewish rituals |
—
|
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: observance of Jewish rituals | Statement: [Donmeh, secretPractice, observance of Jewish rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretPractice Context triple: [Donmeh, secretPractice, observance of Jewish rituals]
-
A.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
B.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
C.
secretDetail
Indicates that one entity reveals or contains confidential or hidden information about another entity or situation.
-
D.
secretProject
Indicates that an entity is involved in, associated with, or designated as a confidential or undisclosed project.
-
E.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f64984819097882c44098b1643 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.