Triple
T4761759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creation of the world |
E105712
|
entity |
| Predicate | narratedInChapter |
P36548
|
FINISHED |
| Object | Genesis 1 |
—
|
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: Genesis 1 | Statement: [Creation of the world, narratedInChapter, Genesis 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narratedInChapter Context triple: [Creation of the world, narratedInChapter, Genesis 1]
-
A.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
B.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
C.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
D.
chapterNumber
Indicates the specific ordinal position a chapter occupies within a larger ordered work, such as a book or document.
-
E.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
- 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.