Triple
T651426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviticus 23:23–25 |
E11352
|
entity |
| Predicate | verses |
P17765
|
FINISHED |
| Object | 23–25 |
—
|
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: 23–25 | Statement: [Leviticus 23:23–25, verses, 23–25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verses Context triple: [Leviticus 23:23–25, verses, 23–25]
-
A.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
B.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
C.
closingVerse
Indicates that one entity serves as the final or concluding verse of another entity, such as a song, poem, or hymn.
-
D.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
E.
verseForm
Indicates the specific structural or metrical pattern in which a verse or poem is composed.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f33b6d881908b6662b73d6fe833 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.