Triple
T7658604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ms. Perkins |
E173446
|
entity |
| Predicate | receivesBountyFor |
P31175
|
FINISHED |
| Object | killing John Wick |
—
|
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: killing John Wick | Statement: [Ms. Perkins, receivesBountyFor, killing John Wick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesBountyFor Context triple: [Ms. Perkins, receivesBountyFor, killing John Wick]
-
A.
bounty
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
-
B.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
C.
awardedForToReceive
Indicates that an entity is granted an award or recognition in order to receive it for a specific reason, achievement, or qualifying basis.
-
D.
grantedAsRewardFor
chosen
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
-
E.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:59 p.m.