Triple

T36953753
Position Surface form Disambiguated ID Type / Status
Subject Gears 5 E914137 entity
Predicate hasExpansion P8606 FINISHED
Object Gears 5: Hivebusters
Gears 5: Hivebusters is a story-driven expansion for the third-person shooter Gears 5, following a new squad on a high-risk mission set in the Gears of War universe.
E2220263 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: Gears 5: Hivebusters | Statement: [Gears 5, hasExpansion, Gears 5: Hivebusters]
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: Gears 5: Hivebusters
Triple: [Gears 5, hasExpansion, Gears 5: Hivebusters]
Generated description
Gears 5: Hivebusters is a story-driven expansion for the third-person shooter Gears 5, following a new squad on a high-risk mission set in the Gears of War universe.

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_69f76e8b28848190abd81fe7a7374910 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9fefe59048190b0661fec4be7651a completed May 5, 2026, 2:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a405112c850819085d4b5a23a67b363 completed June 27, 2026, 10:39 p.m.
NEDg Description generation batch_6a4051cb77588190bb567262099da867 completed June 27, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a4052a4a25881909cf695660c11d30a completed June 27, 2026, 10:45 p.m.
Created at: May 3, 2026, 4:13 p.m.