Triple
T30157308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Too Close – Microsoft Internet Explorer 9 advertising campaign |
E766555
|
entity |
| Predicate | effectOnSong |
P53074
|
FINISHED |
| Object | boosted global popularity of Too Close |
—
|
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: boosted global popularity of Too Close | Statement: [Too Close – Microsoft Internet Explorer 9 advertising campaign, effectOnSong, boosted global popularity of Too Close]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnSong Context triple: [Too Close – Microsoft Internet Explorer 9 advertising campaign, effectOnSong, boosted global popularity of Too Close]
-
A.
effectOfSong
Indicates the influence or impact that a particular song has on something, such as a listener, mood, or situation.
-
B.
songBehavior
Indicates how an entity typically performs, uses, or interacts with a song in a given context.
-
C.
effectOnUsage
Indicates how one factor or condition changes the way something is used, including the extent, manner, or frequency of its usage.
-
D.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:21 p.m.