Triple
T21851984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book III of Psalms |
E539524
|
entity |
| Predicate | traditionallyDividedBy |
P23759
|
FINISHED |
| Object | doxologies in the Psalter |
—
|
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: doxologies in the Psalter | Statement: [Book III of Psalms, traditionallyDividedBy, doxologies in the Psalter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyDividedBy Context triple: [Book III of Psalms, traditionallyDividedBy, doxologies in the Psalter]
-
A.
traditionallyDividedInto
chosen
Indicates that something is customarily or historically separated into specific parts, sections, or categories according to established tradition.
-
B.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
C.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
D.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
E.
typicalDivision
Indicates that one entity is a standard or characteristic subdivision or component of another entity.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0bd59bcbc819093829feb152e090d |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.