Triple

T9477269
Position Surface form Disambiguated ID Type / Status
Subject Intelligent Systems E228546 entity
Predicate knownForGenre P88335 FINISHED
Object tactical role-playing games 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: tactical role-playing games | Statement: [Intelligent Systems, knownForGenre, tactical role-playing games]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownForGenre
Context triple: [Intelligent Systems, knownForGenre, tactical role-playing games]
  • A. knownForMusicGenre
    Indicates that an entity is recognized or notable for producing, performing, or being associated with a particular music genre.
  • B. alsoKnownFor
    Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
  • C. formerlyKnownFor
    Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
  • D. laterKnownFor
    Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
  • E. knownForStoryline
    Indicates that an entity is recognized or notable specifically for its narrative or storyline.
  • 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_69ca847162c48190b079076c9595513c completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd801386948190890133f622ff360b completed April 1, 2026, 8:29 p.m.
PD Predicate disambiguation batch_69cca55f01b081908dc0f12eaa45f832 completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca89d0f0c8190b4528990fe708fca completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:54 p.m.