Triple
T4768447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 89 |
E105867
|
entity |
| Predicate | canonicalNumberingInHebrew |
P6325
|
FINISHED |
| Object | 89 |
—
|
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: 89 | Statement: [Psalm 89, canonicalNumberingInHebrew, 89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalNumberingInHebrew Context triple: [Psalm 89, canonicalNumberingInHebrew, 89]
-
A.
representsNumberInHebrewNumerals
Indicates that one entity is used to represent the numerical value of another entity using Hebrew numeral notation.
-
B.
numericalValueHebrewGematria
Indicates that a numerical value is assigned to text based on Hebrew gematria, where Hebrew letters correspond to specific numbers and their sum yields the value.
-
C.
positionInHebrewBible
chosen
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
D.
transliteratedAsInModernIsraeliUsage
Indicates that one entity is the modern Israeli Hebrew transliteration form used to represent the other entity.
-
E.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.