Triple
T2652097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bnei Mikra |
E53922
|
entity |
| Predicate | hasTheologicalCharacteristic |
P33315
|
FINISHED |
| Object | non-rabbinic Judaism |
—
|
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: non-rabbinic Judaism | Statement: [Bnei Mikra, hasTheologicalCharacteristic, non-rabbinic Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheologicalCharacteristic Context triple: [Bnei Mikra, hasTheologicalCharacteristic, non-rabbinic Judaism]
-
A.
hasDoctrinalCharacteristic
chosen
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
-
B.
hasTheologicalPurpose
Indicates that something is intended or designed to serve a religious or theological function or goal.
-
C.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
D.
theologicalConcept
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
E.
theologicalCategory
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.