Triple
T28856136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 121 |
E728741
|
entity |
| Predicate | numberingInGreekLatinTradition |
P58462
|
FINISHED |
| Object | Psalm 120 |
—
|
NE NERFINISHED |
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: Psalm 120 | Statement: [Psalm 121, numberingInGreekLatinTradition, Psalm 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberingInGreekLatinTradition Context triple: [Psalm 121, numberingInGreekLatinTradition, Psalm 120]
-
A.
numberingInGreek
Indicates that something is assigned or expressed using Greek numeral symbols or a Greek-based numbering system.
-
B.
numberingInSeptuagintVulgate
chosen
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
C.
numericValueInGreekNumerals
Indicates that a given numeric value is represented or expressed using Greek numeral notation.
-
D.
usesGreekLetterSystem
Indicates that one entity employs a writing, naming, or notation system based on Greek letters in relation to another entity or context.
-
E.
laterNumberingSystem
Indicates that one numbering system was adopted or used after another, reflecting a subsequent or more recent scheme of numbering.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 28, 2026, 6:45 a.m.