Triple
T16323088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love is in the Bin |
E396345
|
entity |
| Predicate | wasShreddedImmediatelyAfter |
P57903
|
FINISHED |
| Object | hammer price was announced |
—
|
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: hammer price was announced | Statement: [Love is in the Bin, wasShreddedImmediatelyAfter, hammer price was announced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasShreddedImmediatelyAfter Context triple: [Love is in the Bin, wasShreddedImmediatelyAfter, hammer price was announced]
-
A.
scrappedAfter
chosen
Indicates that one entity was discarded, removed, or abandoned after another specified event or entity in time.
-
B.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
C.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
D.
wasDiscoveredSoonAfter
Indicates that one event, object, or fact was discovered a relatively short time after another specified reference point or event.
-
E.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
- 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.