Triple

T5782914
Position Surface form Disambiguated ID Type / Status
Subject Toby E128202 entity
Predicate hasRelatedName P3889 FINISHED
Object Tobiah E319262 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: Tobiah | Statement: [Toby, hasRelatedName, Tobiah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tobiah
Context triple: [Toby, hasRelatedName, Tobiah]
  • A. Tobiah the Ammonite chosen
    Tobiah the Ammonite is a biblical figure known as one of the chief opponents of Nehemiah’s efforts to rebuild Jerusalem’s walls after the Babylonian exile.
  • B. Eleazar
    Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
  • C. Reuel
    Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
  • D. Reuel
    Reuel is the middle name of famed English author and philologist J. R. R. Tolkien, used as part of his full name John Ronald Reuel Tolkien.
  • E. Berechiah
    Berechiah is a biblical figure mentioned in the Hebrew Bible as part of the priestly and prophetic lineage associated with the prophet Zechariah.
  • 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_69c0084450048190bc647b649a05136b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02a184870819084251554eae1e33c completed March 22, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69c07e7a1cb88190980e0cf675aaa906 completed March 22, 2026, 11:42 p.m.
Created at: March 22, 2026, 3:50 p.m.