Triple
T5345856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 49 |
E124052
|
entity |
| Predicate | canonicalNumberingInGreekLatin |
P58462
|
FINISHED |
| Object | 48 |
—
|
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: 48 | Statement: [Psalm 49, canonicalNumberingInGreekLatin, 48]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalNumberingInGreekLatin Context triple: [Psalm 49, canonicalNumberingInGreekLatin, 48]
-
A.
numericValueInGreekNumerals
Indicates that a given numeric value is represented or expressed using Greek numeral notation.
-
B.
canonicalNumberingInMostEnglishBibles
Indicates that the entity is ordered or numbered according to the standard canonical sequence used in most English-language Bibles.
-
C.
numberingInSeptuagintVulgate
chosen
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
D.
IPAValueAncientGreek
Indicates the International Phonetic Alphabet (IPA) pronunciation value associated with a form in Ancient Greek.
-
E.
hasNumericValueInGreekNumerals
Indicates that an entity is associated with a specific numeric value expressed using Greek numeral notation.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ec46ac81908e45ffb1b7a71507 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.