Triple

T28899306
Position Surface form Disambiguated ID Type / Status
Subject Metro City E732909 entity
Predicate appearsInWork P795 FINISHED
Object Final Fight 2
Final Fight 2 is a side-scrolling beat 'em up video game developed and published by Capcom for the Super Nintendo Entertainment System as a sequel to the original Final Fight.
E1847826 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: Final Fight 2 | Statement: [Metro City, appearsInWork, Final Fight 2]
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: Final Fight 2
Triple: [Metro City, appearsInWork, Final Fight 2]
Generated description
Final Fight 2 is a side-scrolling beat 'em up video game developed and published by Capcom for the Super Nintendo Entertainment System as a sequel to the original Final Fight.

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_69f05b08c2008190ac426a035a2ed66d completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65aa677948190ab5b5a097d4cea5d completed May 2, 2026, 8:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a251f522be48190b004e909e3efd59e completed June 7, 2026, 7:35 a.m.
NEDg Description generation batch_6a2523ff3900819093dcccd970c9cea5 completed June 7, 2026, 7:55 a.m.
NED2 Entity disambiguation (via description) batch_6a2527e117c88190989c7965f5d99f87 completed June 7, 2026, 8:12 a.m.
Created at: April 28, 2026, 8:01 a.m.