Triple
T33502513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry Black |
E858030
|
entity |
| Predicate | personalCost |
P78845
|
FINISHED |
| Object | sacrifices personal stability for the case |
—
|
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: sacrifices personal stability for the case | Statement: [Jerry Black, personalCost, sacrifices personal stability for the case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalCost Context triple: [Jerry Black, personalCost, sacrifices personal stability for the case]
-
A.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
B.
humanCost
chosen
Indicates the extent of harm, suffering, or loss experienced by people as a consequence of an action, event, or decision.
-
C.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
D.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
E.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59cb7ac81909531fb256dadb474 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.