Triple
T57068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Giving Pledge |
E1128
|
entity |
| Predicate | commitmentTiming |
P2796
|
FINISHED |
| Object | during lifetime or in will |
—
|
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: during lifetime or in will | Statement: [The Giving Pledge, commitmentTiming, during lifetime or in will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commitmentTiming Context triple: [The Giving Pledge, commitmentTiming, during lifetime or in will]
-
A.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
B.
typicalAnnouncementTime
Indicates the usual or standard time at which an announcement is made or expected to occur.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24b90ab24819085478dbe95f717dd |
completed | Feb. 28, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.