Triple

T37897067
Position Surface form Disambiguated ID Type / Status
Subject Townlong Steppes E945309 entity
Predicate containsSubzone P6793 FINISHED
Object Gao-Ran Battlefront
Gao-Ran Battlefront is a Pandaria battlefield subzone in World of Warcraft where players fight mantid forces along the western edge of the Townlong Steppes.
E2246574 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: Gao-Ran Battlefront | Statement: [Townlong Steppes, containsSubzone, Gao-Ran Battlefront]
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: Gao-Ran Battlefront
Triple: [Townlong Steppes, containsSubzone, Gao-Ran Battlefront]
Generated description
Gao-Ran Battlefront is a Pandaria battlefield subzone in World of Warcraft where players fight mantid forces along the western edge of the Townlong Steppes.

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_69f76ef0e8708190987c7254ed8c7abe completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a01b999db4c8190bdf1f734199f4a66 completed May 11, 2026, 11:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a41043e22a88190ab6aab3ec60808ae completed June 28, 2026, 11:23 a.m.
NEDg Description generation batch_6a4104c79fb0819084b62acaa5ae7237 completed June 28, 2026, 11:25 a.m.
NED2 Entity disambiguation (via description) batch_6a41059ef42c81909a94722a1563fcd1 completed June 28, 2026, 11:29 a.m.
Created at: May 3, 2026, 4:19 p.m.