Triple
T5373356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalekites |
E108902
|
entity |
| Predicate | commandSourceText |
P409
|
FINISHED |
| Object | Deuteronomy 25:17-19 |
—
|
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: Deuteronomy 25:17-19 | Statement: [Amalekites, commandSourceText, Deuteronomy 25:17-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandSourceText Context triple: [Amalekites, commandSourceText, Deuteronomy 25:17-19]
-
A.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
commandName
Indicates the specific label or identifier used to denote a particular command within a system or interface.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandInputFormat
Indicates the expected structure or syntax that a command must follow when being provided as input.
-
E.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
- F. None of above.
Provenance (3 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.