Triple
T4935608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abimelech |
E110803
|
entity |
| Predicate | requestedToBeKilledBy |
P60485
|
FINISHED |
| Object | his armor-bearer |
—
|
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: his armor-bearer | Statement: [Abimelech, requestedToBeKilledBy, his armor-bearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedToBeKilledBy Context triple: [Abimelech, requestedToBeKilledBy, his armor-bearer]
-
A.
attemptedToKill
Indicates that one entity took deliberate action with the intention of causing the death of another entity, regardless of whether the death actually occurred.
-
B.
killedBy
Indicates that one entity caused the death of another entity.
-
C.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
D.
considersKilling
Indicates that one entity is contemplating or evaluating the possibility of killing another entity.
-
E.
killedAt
Indicates that a killing event occurred at a specific location or time associated with the entities involved.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706825188190b854dca5ca2f9db6 |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:30 p.m.