Triple
T2073429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebus |
E44866
|
entity |
| Predicate | religiousTextTradition |
P34765
|
FINISHED |
| Object | 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: Judaism | Statement: [Jebus, religiousTextTradition, Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTextTradition Context triple: [Jebus, religiousTextTradition, Judaism]
-
A.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
B.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
D.
religiousCulturalContext
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
E.
partOfReligiousTradition
Indicates that one entity belongs to, is included within, or is practiced as a component of a particular religious tradition.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba101c008190840763d2f28fa8d7 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.