Triple
T21592516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviathan |
E532814
|
entity |
| Predicate | describedInPsalm74As |
P144086
|
FINISHED |
| Object | multi-headed sea monster |
—
|
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: multi-headed sea monster | Statement: [Leviathan, describedInPsalm74As, multi-headed sea monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInPsalm74As Context triple: [Leviathan, describedInPsalm74As, multi-headed sea monster]
-
A.
psalmUsed
Indicates that one entity makes use of, references, or incorporates a particular psalm in some context or activity.
-
B.
relatedPsalm
Indicates that one entity is a psalm that is thematically, liturgically, or contextually associated with another entity.
-
C.
psalmNumber
Indicates the specific numerical designation assigned to a psalm within an ordered collection or canon.
-
D.
psalmSuperscription
Indicates that a psalm is associated with a particular superscription, such as a heading or introductory note that frames its context or use.
-
E.
functionInPsalter
Indicates the specific liturgical, structural, or thematic role that a psalm (or part of it) serves within the overall collection of the Psalter.
- F. None of above. chosen
Provenance (4 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadeb56c8190bce79efadf3c644d |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:32 p.m.