Triple
T23876918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Méphistophélès |
E592891
|
entity |
| Predicate | bargainsFor |
P154291
|
FINISHED |
| Object | human souls |
—
|
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: human souls | Statement: [Méphistophélès, bargainsFor, human souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bargainsFor Context triple: [Méphistophélès, bargainsFor, human souls]
-
A.
offersDiscountsOn
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
B.
conditionOfBargain
Indicates that one entity is a term, stipulation, or requirement that forms part of the agreed exchange in a bargain or contract.
-
C.
PaulOffers
Indicates that Paul presents or proposes something (such as help, goods, or an opportunity) to another party for their consideration or acceptance.
-
D.
buys
Indicates that one entity purchases or acquires something from another entity, typically in exchange for money or other compensation.
-
E.
offeredBundle
Indicates that one entity has presented a specific combination of items or services together as a bundled offer to another entity.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:15 p.m.