Triple
T1194825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 117 |
E25643
|
entity |
| Predicate | containsImperative |
P25671
|
FINISHED |
| Object | Praise the Lord |
—
|
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: Praise the Lord | Statement: [Psalm 117, containsImperative, Praise the Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsImperative Context triple: [Psalm 117, containsImperative, Praise the Lord]
-
A.
hasImperativeEnding
Indicates that an expression concludes with a verb form or construction that conveys an imperative (command or directive) mood.
-
B.
isCommandedIn
Indicates that an entity is under the authority or control of another entity within a specific context, such as a mission, operation, or organizational structure.
-
C.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
D.
imposes
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd78f61c8190bdba2255d35a8fe4 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.