Triple
T1451126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nostra Aetate |
E31292
|
entity |
| Predicate | sectionNumberDiscussingJudaism |
P28750
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Nostra Aetate, sectionNumberDiscussingJudaism, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionNumberDiscussingJudaism Context triple: [Nostra Aetate, sectionNumberDiscussingJudaism, 4]
-
A.
judaismView
Indicates a relationship where one entity holds a particular view, interpretation, or doctrinal position within or about Judaism regarding another entity or topic.
-
B.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
C.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
D.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
E.
halachicNote
Indicates a relationship where one entity serves as a halachic (Jewish legal) note, comment, or annotation providing legal clarification or guidance about another entity.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57bc0908190a57e6bc3d20d5e3c |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.