Triple
T9036227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 133 |
E216499
|
entity |
| Predicate | hasAlternativeNumbering |
P22023
|
FINISHED |
| Object | 132 in the Septuagint |
—
|
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: 132 in the Septuagint | Statement: [Psalm 133, hasAlternativeNumbering, 132 in the Septuagint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNumbering Context triple: [Psalm 133, hasAlternativeNumbering, 132 in the Septuagint]
-
A.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
B.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
C.
usesHarmonizedNumberingWith
chosen
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
D.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6ac0b00c8190a7250b86bb7cc276 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.