Triple
T36923759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Melmoth |
E913277
|
entity |
| Predicate | paysWith |
P84088
|
FINISHED |
| Object | his soul |
—
|
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: his soul | Statement: [John Melmoth, paysWith, his soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paysWith Context triple: [John Melmoth, paysWith, his soul]
-
A.
pays
Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
-
B.
paymentSystem
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
-
C.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
-
D.
payType
chosen
Indicates the method or category of payment used in a transaction or compensation arrangement.
-
E.
canPay
Indicates that one entity has the ability or authorization to make a payment to another entity or to settle a specified obligation.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdcee55c8190ac5c514365310457 |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.