Triple
T33502508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry Black |
E858030
|
entity |
| Predicate | promiseContext |
P177046
|
FINISHED |
| Object | made pledge at the child’s funeral |
—
|
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: made pledge at the child’s funeral | Statement: [Jerry Black, promiseContext, made pledge at the child’s funeral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promiseContext Context triple: [Jerry Black, promiseContext, made pledge at the child’s funeral]
-
A.
promiseScope
Indicates that one entity has made a commitment or assurance to another entity regarding a specific action, condition, or outcome within a defined scope or context.
-
B.
promiseProperty
Indicates that one entity has made a commitment or assurance to another regarding a specific property or attribute.
-
C.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
D.
corePromise
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
-
E.
keptPromiseTo
Indicates that one entity fulfilled or honored a promise previously made to another entity.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:38 a.m.