Triple

T37945917
Position Surface form Disambiguated ID Type / Status
Subject Sony Ericsson P900 E946605 entity
Predicate supportsHtmlBrowsing P146164 FINISHED
Object yes 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: yes | Statement: [Sony Ericsson P900, supportsHtmlBrowsing, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsHtmlBrowsing
Context triple: [Sony Ericsson P900, supportsHtmlBrowsing, yes]
  • A. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • B. supportsOnlineContent
    Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
  • C. hasBrowseFunction chosen
    Indicates that an entity possesses the capability to browse or access external information sources (such as the web or documents).
  • D. supportsJavaScriptAPIs
    Indicates that one entity provides or is compatible with JavaScript-based application programming interfaces for use by another entity.
  • E. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • 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_69f76ef531ac8190ae6d99e5786e76ec completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a037c903be48190a2fafa53d7d50d42 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a192a008190a9917688a9e804f4 completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:20 p.m.