Triple
T6806159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 135 |
E156310
|
entity |
| Predicate | hasNumberingVariant |
P39721
|
FINISHED |
| Object | Septuagint/Vulgate numbering |
—
|
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: Septuagint/Vulgate numbering | Statement: [Psalm 135, hasNumberingVariant, Septuagint/Vulgate numbering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberingVariant Context triple: [Psalm 135, hasNumberingVariant, Septuagint/Vulgate numbering]
-
A.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
B.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
C.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
D.
workNumberingVariant
chosen
Indicates that one work serves as an alternative or variant numbering representation of another work within a numbering or cataloging system.
-
E.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d3082dcc8190a84bc056236cc52e |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.