Triple
T22369211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 24 |
E552993
|
entity |
| Predicate | answerGiven |
P147392
|
FINISHED |
| Object | "The Lord strong and mighty, the Lord mighty in battle" |
—
|
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: "The Lord strong and mighty, the Lord mighty in battle" | Statement: [Psalm 24, answerGiven, "The Lord strong and mighty, the Lord mighty in battle"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: answerGiven Context triple: [Psalm 24, answerGiven, "The Lord strong and mighty, the Lord mighty in battle"]
-
A.
answeredBy
Indicates that a question, request, or problem is responded to or resolved by a particular entity.
-
B.
givenAs
Indicates that something is provided, presented, or assigned to a recipient in a specified role, form, or capacity.
-
C.
hasGiven
Indicates that one entity has transferred or presented something to another entity.
-
D.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
E.
typicalAnswerType
Indicates the usual or expected kind of entity or value that serves as an answer to a given question or query.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158032b748190ad36c7e3809304e9 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.