Triple
T112905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodox Judaism |
E2285
|
entity |
| Predicate | views |
P2235
|
FINISHED |
| Object | Written Torah and Oral Torah as divinely revealed |
—
|
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: Written Torah and Oral Torah as divinely revealed | Statement: [Orthodox Judaism, views, Written Torah and Oral Torah as divinely revealed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: views Context triple: [Orthodox Judaism, views, Written Torah and Oral Torah as divinely revealed]
-
A.
vision
Indicates that an entity perceives another entity or object visually, using sight.
-
B.
viewsGraceAs
Indicates that one entity regards or perceives Grace in a particular way or role.
-
C.
opinionBy
chosen
Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
overlooks
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.