Triple
T34376749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yetûr |
E882305
|
entity |
| Predicate | hasScriptureRole |
P120579
|
FINISHED |
| Object | genealogical figure |
—
|
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: genealogical figure | Statement: [Yetûr, hasScriptureRole, genealogical figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptureRole Context triple: [Yetûr, hasScriptureRole, genealogical figure]
-
A.
hasScripturalRole
chosen
Indicates that an entity holds a specific role, function, or position within a scriptural or religious text.
-
B.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
-
D.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
E.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:59 a.m.