Triple

T9024887
Position Surface form Disambiguated ID Type / Status
Subject PAJN E216020 entity
Predicate supportsScheduledCommercialService P85912 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: [PAJN, supportsScheduledCommercialService, Yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsScheduledCommercialService
Context triple: [PAJN, supportsScheduledCommercialService, Yes]
  • A. announcedCommercialService
    Indicates that an entity has publicly declared the start or availability of a commercial service involving another entity.
  • B. hasAdSupportedTier
    Indicates that an entity offers or includes a tier, plan, or version that is supported by advertising.
  • C. supportsDisplayStandard
    Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
  • D. usedForTelevisionBroadcastSchedules
    Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
  • E. hasStreamingEligibility
    Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
  • F. None of above. chosen

Provenance (4 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_69ca83a5fa88819088144801b4dd7245 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a7b902c81909fcbdc433a1acf7a completed April 1, 2026, 12:44 a.m.
PD Predicate disambiguation batch_69cc5ee132f08190940749c7c522e4c1 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f887108819096d45a186fc137b3 completed March 31, 2026, 11:58 p.m.
Created at: March 30, 2026, 7:07 p.m.