Triple

T742233
Position Surface form Disambiguated ID Type / Status
Subject Tribe of Judah E15267 entity
Predicate ancestorDescribedAs P18871 FINISHED
Object fourth son of Jacob 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: fourth son of Jacob | Statement: [Tribe of Judah, ancestorDescribedAs, fourth son of Jacob]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ancestorDescribedAs
Context triple: [Tribe of Judah, ancestorDescribedAs, fourth son of Jacob]
  • A. ancestor
    Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
  • B. derivedFrom
    Indicates that one entity originates, is obtained, or is developed from another source entity.
  • C. grandparent
    Indicates that one entity is the parent of another entity’s parent.
  • D. auntOf
    Indicates that one person is the aunt of another, typically as the sibling (or sibling-in-law) of a parent or sometimes an older female relative in an extended family role.
  • E. inheritedFrom
    Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
  • 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_69a49358aa308190adbc9b5a0a2adcf9 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a60e286c81908787a41cf9b9f150 completed March 1, 2026, 8:48 p.m.
PD Predicate disambiguation batch_69a4a4fdaaf48190985f62acfc069508 completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a5a35c68819082429755c046e9a7 completed March 1, 2026, 8:46 p.m.
Created at: March 1, 2026, 7:37 p.m.