Triple
T5718030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joshua |
E126068
|
entity |
| Predicate | etymologicallyDerivedFrom |
P453
|
FINISHED |
| Object | Yehoshua |
E406976
|
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: Yehoshua | Statement: [Joshua, etymologicallyDerivedFrom, Yehoshua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yehoshua Context triple: [Joshua, etymologicallyDerivedFrom, Yehoshua]
-
A.
Yoshua
Yoshua is a male given name most notably borne by Yoshua Bengio, a pioneering Canadian computer scientist and deep learning researcher.
-
B.
Joshua
Joshua is a masculine given name of Hebrew origin, commonly used in English-speaking countries.
-
C.
Joshua
chosen
Joshua is a central biblical leader who succeeded Moses, led the Israelites into the Promised Land, and is the namesake of the Book of Joshua in the Hebrew Bible.
-
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.
Ehud
Ehud is a biblical judge and deliverer of Israel known for assassinating the Moabite king Eglon in the Book of Judges.
- 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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024e084cc81909a652f7c10d32c32 |
completed | March 22, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e337729081909ff1a9d4cd20eeb9 |
completed | March 23, 2026, 6:52 a.m. |
Created at: March 22, 2026, 3:46 p.m.