Triple

T27730566
Position Surface form Disambiguated ID Type / Status
Subject Gamerscore E697419 entity
Predicate persistsAcross P11419 FINISHED
Object console generations 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: console generations | Statement: [Gamerscore, persistsAcross, console generations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: persistsAcross
Context triple: [Gamerscore, persistsAcross, console generations]
  • A. persistsAfter
    Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
  • B. persistence chosen
    Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
  • C. supportsPersistence
    Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
  • D. preservedFor
    Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
  • E. maintainsThrough
    Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6895f0819088655277e45859a8 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 3:11 p.m.