Triple
T6306952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 76 |
E141400
|
entity |
| Predicate | keyImage |
P69964
|
FINISHED |
| Object | God breaking the weapons of war |
—
|
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: God breaking the weapons of war | Statement: [Psalm 76, keyImage, God breaking the weapons of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyImage Context triple: [Psalm 76, keyImage, God breaking the weapons of war]
-
A.
keyIndex
Indicates the position or numerical index assigned to a specific key within an ordered set or collection of keys.
-
B.
keyExport
Indicates that a cryptographic key is transferred or made available from one system, location, or format to another.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyOperation
Indicates an operation that is central, primary, or essential to the functioning or outcome of another process, system, or relationship.
-
E.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0647b69f08190bb085f9b700f6453 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.