Triple
T36401148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Applegate |
E896629
|
entity |
| Predicate | makesFaustianBargainWith |
P86550
|
FINISHED |
| Object | Joe Boyd |
—
|
NE NERFINISHED |
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: Joe Boyd | Statement: [Mr. Applegate, makesFaustianBargainWith, Joe Boyd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesFaustianBargainWith Context triple: [Mr. Applegate, makesFaustianBargainWith, Joe Boyd]
-
A.
protagonistMakesPactWith
chosen
Indicates that the protagonist enters into a formal or binding agreement, often with significant consequences, with another entity.
-
B.
makesPactFor
Indicates that one entity enters into a formal agreement or pact on behalf of, or for the benefit of, another entity.
-
C.
usesDeceptionTo
Indicates that one entity employs deceit or misleading tactics in order to influence, manipulate, or achieve an outcome involving another entity.
-
D.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
E.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.