Triple
T5798891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirteen Principles of Faith |
E128571
|
entity |
| Predicate | aimsToDefine |
P38243
|
FINISHED |
| Object | core Jewish beliefs |
—
|
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: core Jewish beliefs | Statement: [Thirteen Principles of Faith, aimsToDefine, core Jewish beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToDefine Context triple: [Thirteen Principles of Faith, aimsToDefine, core Jewish beliefs]
-
A.
definesAimsOf
chosen
Indicates that one entity specifies or establishes the goals, purposes, or intended outcomes of another entity.
-
B.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
D.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
E.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.