Triple

T5260586
Position Surface form Disambiguated ID Type / Status
Subject Battle of Ai E118812 entity
Predicate scripturalBook P5309 FINISHED
Object Joshua E21599 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: Joshua | Statement: [Battle of Ai, scripturalBook, Joshua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Joshua
Context triple: [Battle of Ai, scripturalBook, Joshua]
  • A. Joshua chosen
    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.
  • B. Joshua
    Joshua is a masculine given name of Hebrew origin, commonly used in English-speaking countries.
  • C. Joshua
    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. Yoshua
    Yoshua is a male given name most notably borne by Yoshua Bengio, a pioneering Canadian computer scientist and deep learning researcher.
  • E. Joshua son of Jehozadak
    Joshua son of Jehozadak was the high priest of the Jewish community during the early post-exilic period, serving alongside Zerubbabel in the rebuilding and restoration of worship at the Second Temple in Jerusalem.
  • 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_69bd446a42c88190b7ecbef006561d55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7bcf026c8190881b6e14b962a3c9 completed March 20, 2026, 4:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf18770e608190932d9de276e47212 completed March 21, 2026, 10:15 p.m.
Created at: March 20, 2026, 1:50 p.m.