Triple
T35249812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammonites |
E1018065
|
entity |
| Predicate | roleInHebrewBible |
P203196
|
FINISHED |
| Object | adversaries of the Israelites |
—
|
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: adversaries of the Israelites | Statement: [Ammonites, roleInHebrewBible, adversaries of the Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHebrewBible Context triple: [Ammonites, roleInHebrewBible, adversaries of the Israelites]
-
A.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
B.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
C.
roleInJoshua
Indicates that an entity holds a specific role or function within the context of the Book of Joshua or its narrative events.
-
D.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
E.
roleInTalmud
Indicates that one entity holds a specific role, function, or status within the context of the Talmud.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01378bf05c8190af9f5e06a2810c7d |
completed | May 11, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_6a0137277c6c8190bcec341f2a0757c4 |
completed | May 11, 2026, 1:55 a.m. |
| PDg | Predicate description generation | batch_6a01378b165c8190b7b738da4e1ab36b |
completed | May 11, 2026, 1:57 a.m. |
Created at: May 3, 2026, 4:02 p.m.