Triple

T38645128
Position Surface form Disambiguated ID Type / Status
Subject MBCGame Starleague E938694 entity
Predicate developedAudience P62009 FINISHED
Object StarCraft: Brood War fans 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: StarCraft: Brood War fans | Statement: [MBCGame Starleague, developedAudience, StarCraft: Brood War fans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: developedAudience
Context triple: [MBCGame Starleague, developedAudience, StarCraft: Brood War fans]
  • A. typicalAudience
    Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
  • B. secondaryAudience
    Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
  • C. relatesToAudience chosen
    Indicates a general relationship or relevance between something and a particular audience or group of recipients.
  • D. audienceDescribedAs
    Indicates that an audience is characterized or labeled using a particular description or set of attributes.
  • E. targetDevelopers
    Indicates that something is specifically aimed at, intended for, or directed toward developers as its primary audience or users.
  • 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_69f76ed948ec81908ce7811608a8f359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe629b4fa481908467c7c41b77f0c6 completed May 8, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69fe61bb260c819083f9378a3a06ca47 completed May 8, 2026, 10:20 p.m.
Created at: May 3, 2026, 4:32 p.m.