Triple
T1215691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasidism |
E26100
|
entity |
| Predicate | hasViewOnSecularCulture |
P25076
|
FINISHED |
| Object | restrictive |
—
|
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: restrictive | Statement: [Hasidism, hasViewOnSecularCulture, restrictive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnSecularCulture Context triple: [Hasidism, hasViewOnSecularCulture, restrictive]
-
A.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
B.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
C.
religiousCulturalContext
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
D.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
E.
hasViewOnLaity
Indicates that one entity holds a particular stance, opinion, or doctrinal position regarding the role or nature of laypeople.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be059c5c8190a200f09442c22334 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.