Triple
T15477698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Araunah the Jebusite |
E376826
|
entity |
| Predicate | responseFromDavid |
P19418
|
FINISHED |
| Object | David insisted on paying full price |
—
|
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: David insisted on paying full price | Statement: [Araunah the Jebusite, responseFromDavid, David insisted on paying full price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseFromDavid Context triple: [Araunah the Jebusite, responseFromDavid, David insisted on paying full price]
-
A.
responseOfDavid
Indicates that something is a response given by David to a prior message, event, or situation.
-
B.
responseFrom
chosen
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
C.
responseFormula
Indicates that one entity’s reaction, reply, or outcome is expressed or encoded in a specific formula or structured representation.
-
D.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
E.
respondUsage
Indicates that one entity replies or reacts in some manner to the use or application of another entity.
- 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_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. |
Created at: April 10, 2026, 3:34 a.m.