Triple
T16254230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 33:23 |
E394587
|
entity |
| Predicate | positionWithinTribalBlessings |
P46638
|
FINISHED |
| Object | blessing of Naphtali |
—
|
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: blessing of Naphtali | Statement: [Deuteronomy 33:23, positionWithinTribalBlessings, blessing of Naphtali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinTribalBlessings Context triple: [Deuteronomy 33:23, positionWithinTribalBlessings, blessing of Naphtali]
-
A.
associatedWithBlessing
chosen
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
B.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
C.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
D.
positionOnRitual
Indicates the stance, role, or placement an entity holds with respect to a particular ritual or ceremonial practice.
-
E.
tribalRestriction
Indicates a limitation, condition, or rule that applies specifically based on tribal affiliation or tribal status.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.