Triple

T11204177
Position Surface form Disambiguated ID Type / Status
Subject Miles&Go E265116 entity
Predicate supportsMobileApp P14571 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: [Miles&Go, supportsMobileApp, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsMobileApp
Context triple: [Miles&Go, supportsMobileApp, yes]
  • A. supportsMobileWallets
    Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
  • B. hasApp chosen
    Indicates that an entity possesses, provides, or is associated with a particular application.
  • C. supportedPlatform
    Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
  • D. supportedWork
    Indicates that one entity provides assistance, resources, or endorsement to enable or sustain the work or activity of another entity.
  • E. supportsThirdPartyApplications
    Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d355c481908fc3d555b596314d completed April 9, 2026, 5:58 p.m.
PD Predicate disambiguation batch_69d75cf83464819087529d47d025d313 completed April 9, 2026, 8:02 a.m.
Created at: April 8, 2026, 9:30 p.m.