Triple

T31269389
Position Surface form Disambiguated ID Type / Status
Subject Joshua 13:22 E797340 entity
Predicate identifiesBalaamAs P173768 FINISHED
Object non-Israelite diviner 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: non-Israelite diviner | Statement: [Joshua 13:22, identifiesBalaamAs, non-Israelite diviner]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: identifiesBalaamAs
Context triple: [Joshua 13:22, identifiesBalaamAs, non-Israelite diviner]
  • A. hasNumberOfProphetsOfBaal
    Indicates the quantity or count of prophets of Baal associated with a given entity.
  • B. namedByGod
    Indicates that an entity has been given its name directly by God.
  • C. regardsAsOnlyProphetAfterMoses
    Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
  • D. roleOfReferencedDeity
    Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
  • E. subjectOfProphecy
    Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
  • 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_69f224de2bbc819081af6c32e1d857b9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6ba1733408190af579d93a7946508 completed May 3, 2026, 2:59 a.m.
PD Predicate disambiguation batch_69f6b6293188819080d5041ca0adb969 completed May 3, 2026, 2:42 a.m.
PDg Predicate description generation batch_69f6b960ca4081909a77690c2b122f5e completed May 3, 2026, 2:56 a.m.
Created at: April 29, 2026, 9:13 p.m.