Triple
T19784845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahimaaz |
E475233
|
entity |
| Predicate | deliveredMessageAbout |
P1386
|
FINISHED |
| Object | Absalom’s plans |
—
|
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: Absalom’s plans | Statement: [Ahimaaz, deliveredMessageAbout, Absalom’s plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveredMessageAbout Context triple: [Ahimaaz, deliveredMessageAbout, Absalom’s plans]
-
A.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
B.
delivered
chosen
Indicates that something has been brought or transported to a recipient or destination, typically completing a transfer or fulfillment of an order, message, or service.
-
C.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
D.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
E.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.