Triple

T30157004
Position Surface form Disambiguated ID Type / Status
Subject Too Close E766548 entity
Predicate usedInCommercial P101201 FINISHED
Object Internet Explorer 9 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: Internet Explorer 9 | Statement: [Too Close, usedInCommercial, Internet Explorer 9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInCommercial
Context triple: [Too Close, usedInCommercial, Internet Explorer 9]
  • A. usedInMarketingMaterials chosen
    Indicates that something is included or featured as part of marketing or promotional materials.
  • B. permitsCommercialUse
    Indicates that an entity grants permission for its use in commercial or profit-generating contexts.
  • C. hasCommercialAppeal
    Indicates that something possesses qualities likely to attract buyers or generate profitable market interest.
  • D. usedInECommerce
    Indicates that something is employed or applied within the context of electronic commerce activities or systems.
  • E. isNonCommercial
    Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
  • 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_69fd44474ed48190ac372e4c88d762ed completed May 8, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69fd41ef28a48190a66959be5c964461 completed May 8, 2026, 1:52 a.m.
Created at: April 29, 2026, 7:21 p.m.