Triple

T4761779
Position Surface form Disambiguated ID Type / Status
Subject Creation of the world E105712 entity
Predicate sourceTextDivision P9883 FINISHED
Object Priestly account (Genesis 1:1–2:4a, in many scholarly views) 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: Priestly account (Genesis 1:1–2:4a, in many scholarly views) | Statement: [Creation of the world, sourceTextDivision, Priestly account (Genesis 1:1–2:4a, in many scholarly views)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sourceTextDivision
Context triple: [Creation of the world, sourceTextDivision, Priestly account (Genesis 1:1–2:4a, in many scholarly views)]
  • A. textFragment chosen
    Indicates that one piece of text is a constituent part or segment of a larger text.
  • B. textContent
    Indicates that one entity is the textual content or written material contained within another entity.
  • C. textualStructure
    Indicates how parts of a text are organized and related to each other within its overall structure.
  • D. canonicalDivision
    Indicates that one entity is the standard or officially recognized subdivision or partition of another entity.
  • E. divisionContext
    Indicates the situational or conceptual setting in which a division operation or separation between entities takes place.
  • F. None of above.

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_69bd43f14cac819081c7c69803648211 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:20 p.m.