Triple
T16323092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love is in the Bin |
E396345
|
entity |
| Predicate | buyerDecision |
P56429
|
FINISHED |
| Object | buyer accepted the work after shredding |
—
|
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: buyer accepted the work after shredding | Statement: [Love is in the Bin, buyerDecision, buyer accepted the work after shredding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buyerDecision Context triple: [Love is in the Bin, buyerDecision, buyer accepted the work after shredding]
-
A.
recipientDecision
chosen
Indicates that a designated recipient makes or has made a choice or judgment regarding a proposal, request, or item.
-
B.
buyer
Indicates a relationship where one entity purchases or acquires goods, services, or rights from another entity in exchange for payment or compensation.
-
C.
requiresDecision
Indicates that a choice or judgment must be made regarding the associated entities or situation.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b82fe88190a448597b7827f859 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.