Triple
T30498651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 57 |
E776076
|
entity |
| Predicate | hasParallelThemesWith |
P57196
|
FINISHED |
| Object | Psalm 56 |
—
|
NE NERFINISHED |
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: Psalm 56 | Statement: [Psalm 57, hasParallelThemesWith, Psalm 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelThemesWith Context triple: [Psalm 57, hasParallelThemesWith, Psalm 56]
-
A.
hasThemeRelationship
Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
-
B.
hasThematicSimilarityTo
Indicates that two entities share related themes, topics, or conceptual content to a notable degree.
-
C.
hasThematicOrigin
Indicates that something originates from, or is thematically derived from, a particular source, subject, or theme.
-
D.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
-
E.
hasConceptualParallel
chosen
Indicates that one entity corresponds to or mirrors another at a conceptual level, showing a similar idea, structure, or pattern despite possible differences in form or context.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 8:14 p.m.