Triple

T28264003
Position Surface form Disambiguated ID Type / Status
Subject Google+ E712652 entity
Predicate consumerVersionShutdown P128529 FINISHED
Object 2019-04-02 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: 2019-04-02 | Statement: [Google+, consumerVersionShutdown, 2019-04-02]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consumerVersionShutdown
Context triple: [Google+, consumerVersionShutdown, 2019-04-02]
  • A. discontinuedInVersionOf
    Indicates that something (such as a feature, product, or component) ceased to be available or supported starting from a specific version of another entity.
  • B. shutdownAnnouncedOn chosen
    Indicates that an official announcement was made on a specific date or platform that a system, service, or operation will be shut down.
  • C. discontinuationAnnouncedBy
    Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
  • D. permanentShutdown
    Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
  • E. discontinuationBy
    Indicates that one entity causes or initiates the stopping, ending, or termination of another entity, process, or activity.
  • 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_69efb5216c6881908020dce4aea65381 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f6441c2ed081909128d8fe21b14fa4 completed May 2, 2026, 6:36 p.m.
PD Predicate disambiguation batch_69f641e0fde08190bf06a1c5b388aa84 completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 11:13 p.m.