Triple
T14853346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 29 |
E349285
|
entity |
| Predicate | narrativeSectionOf |
P115876
|
FINISHED |
| Object | Patriarchal narratives |
—
|
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: Patriarchal narratives | Statement: [Genesis 29, narrativeSectionOf, Patriarchal narratives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeSectionOf Context triple: [Genesis 29, narrativeSectionOf, Patriarchal narratives]
-
A.
narrativeSectionName
Indicates the specific title or label assigned to a section within a narrative or story structure.
-
B.
sectionNarrator
Indicates that a given entity serves as the narrator or narrative voice for a particular section of a work.
-
C.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
D.
narrativeDescription
Indicates that one entity provides a textual or spoken account describing the events, context, or details related to another entity.
-
E.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.