Triple
T1614529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Ta-Ha |
E34684
|
entity |
| Predicate | mentionsProphet |
P831
|
FINISHED |
| Object | Moses |
E11297
|
NE 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: Moses | Statement: [Surah Ta-Ha, mentionsProphet, Moses]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moses Context triple: [Surah Ta-Ha, mentionsProphet, Moses]
-
A.
Moses
chosen
Moses is a central prophet and leader in the Hebrew Bible, traditionally credited with leading the Israelites out of Egypt and receiving the Ten Commandments from God.
-
B.
Moses the Black
Moses the Black was a 4th-century Ethiopian desert monk and former bandit who became a renowned Christian ascetic and saint among the Desert Fathers.
-
C.
Yoshua
Yoshua is a male given name most notably borne by Yoshua Bengio, a pioneering Canadian computer scientist and deep learning researcher.
-
D.
Joshua
Joshua is a book of the Hebrew Bible and Christian Old Testament that narrates the Israelite conquest and settlement of Canaan under the leadership of Joshua.
-
E.
Joshua
Joshua is a masculine given name of Hebrew origin, commonly used in English-speaking countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9098f384c81909ef836ee779466e2 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51ca2bc48190abb83f4d84782334 |
completed | March 8, 2026, 10:39 a.m. |
Created at: March 4, 2026, 7:28 p.m.