Triple
T37501186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Williams |
E931965
|
entity |
| Predicate | replacesHandWith |
P197403
|
FINISHED |
| Object | chainsaw |
—
|
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: chainsaw | Statement: [Ash Williams, replacesHandWith, chainsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesHandWith Context triple: [Ash Williams, replacesHandWith, chainsaw]
-
A.
changedHands
Indicates that ownership or control of something has been transferred from one party to another.
-
B.
handsOverTo
Indicates that one entity transfers possession, control, or responsibility of something directly to another entity.
-
C.
servedAsHandTo
Indicates that one entity functioned as an assistant, aide, or subordinate support to another entity in carrying out tasks or responsibilities.
-
D.
canChangeHandsBy
Indicates that ownership or control of something is able to be transferred from one party to another through a specified means or process.
-
E.
hasHand
Indicates that an entity possesses or is equipped with a hand (or hands) as part of its body or structure.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.