Triple

T29247301
Position Surface form Disambiguated ID Type / Status
Subject Terry Bogard E741472 entity
Predicate team P3756 FINISHED
Object Fatal Fury Team
The Fatal Fury Team is a recurring trio of fighters from SNK’s Fatal Fury series, typically led by Terry Bogard, that appears as a unified team in The King of Fighters crossover fighting games.
E1882965 NE 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: Fatal Fury Team | Statement: [Terry Bogard, team, Fatal Fury Team]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fatal Fury Team
Triple: [Terry Bogard, team, Fatal Fury Team]
Generated description
The Fatal Fury Team is a recurring trio of fighters from SNK’s Fatal Fury series, typically led by Terry Bogard, that appears as a unified team in The King of Fighters crossover fighting games.

Provenance (5 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_69f0911eba2c8190b07cd2fdf91422c9 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f6648a17708190a2b19c610549b5e5 completed May 2, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a26c8ccea4081908af7bebb2bf542d1 completed June 8, 2026, 1:51 p.m.
NEDg Description generation batch_6a26cccde768819084aeb6b6af7db79a completed June 8, 2026, 2:08 p.m.
NED2 Entity disambiguation (via description) batch_6a26d2ec512c8190aa76543315c0ddd2 completed June 8, 2026, 2:34 p.m.
Created at: April 28, 2026, 12:33 p.m.