Triple

T30342583
Position Surface form Disambiguated ID Type / Status
Subject color video tape recorder E771795 entity
Predicate becameCommonIn P81534 FINISHED
Object 1970s 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: 1970s | Statement: [color video tape recorder, becameCommonIn, 1970s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: becameCommonIn
Context triple: [color video tape recorder, becameCommonIn, 1970s]
  • A. becameCommonerOn
    Indicates the date or time at which an entity transitioned from a non-commoner status to becoming a commoner.
  • B. moreCommonIn
    Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
  • C. isLessCommonSince
    Indicates that the frequency or prevalence of one entity has decreased relative to another entity or to its own past occurrence from a specified point in time.
  • D. moreCommonAs
    Indicates that one thing occurs or is observed more frequently in a specified role, form, or context than in another.
  • E. firstWidelyUsedDuring chosen
    Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
  • 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_69f2248b9a208190bc3e6804acd5afd6 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f682046608819091b68c1f04f8f7fe completed May 2, 2026, 11 p.m.
PD Predicate disambiguation batch_69f67603526c81908295a1ece8727c66 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:55 p.m.