Triple

T14374604
Position Surface form Disambiguated ID Type / Status
Subject Mobile Business Group E356440 entity
Predicate brandManager P42952 FINISHED
Object Moto smartphone brand 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: Moto smartphone brand | Statement: [Mobile Business Group, brandManager, Moto smartphone brand]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: brandManager
Context triple: [Mobile Business Group, brandManager, Moto smartphone brand]
  • A. brand
    Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
  • B. brandManaged chosen
    Indicates that one entity is responsible for overseeing, controlling, or administering the brand of another entity.
  • C. brandRepresents
    Indicates that a brand stands for, symbolizes, or conveys the identity, values, or characteristics of something.
  • D. brandAssociationType
    Indicates the specific nature of the relationship or association that exists between a brand and another entity (such as a product, organization, or campaign).
  • E. controlsBrand
    Indicates that one entity has authority over, management of, or decisive influence on the brand 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_69d8279163a081908aec45c0e3f1e02f completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9007184c8190aebb003cb6548cc8 completed April 14, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69de2a9cb3e081909f6b33fdd939bb9e completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:16 a.m.