Triple
T30498634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 57 |
E776076
|
entity |
| Predicate | containsSuperscription |
P198992
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Psalm 57, containsSuperscription, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSuperscription Context triple: [Psalm 57, containsSuperscription, Yes]
-
A.
containsSupplicationOf
Indicates that one entity includes or expresses a plea, request, or supplicatory appeal directed toward another entity.
-
B.
hasSupplement
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
C.
endsUpWith
Indicates that, as a result of some process or sequence of events, one entity ultimately comes to possess, receive, or be associated with another entity.
-
D.
isSuperstring
Indicates that one string contains another string as a contiguous subsequence or in its entirety, making it a superstring of the other.
-
E.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 29, 2026, 8:14 p.m.