Triple
T15477925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asherah pole |
E376832
|
entity |
| Predicate | commandedActionInHebrewBible |
P118408
|
FINISHED |
| Object | destroy |
—
|
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: destroy | Statement: [Asherah pole, commandedActionInHebrewBible, destroy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedActionInHebrewBible Context triple: [Asherah pole, commandedActionInHebrewBible, destroy]
-
A.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
B.
commandmentHebrewName
Indicates the Hebrew-language name assigned to a particular commandment.
-
C.
commandedOperationAgainst
Indicates that one entity issued authoritative orders to initiate or conduct a specific military or strategic operation directed against another entity.
-
D.
containsCommandment
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:34 a.m.