Triple

T28199728
Position Surface form Disambiguated ID Type / Status
Subject Battle of East Stoke E716846 entity
Predicate location P40 FINISHED
Object East Stoke
East Stoke is a village in Nottinghamshire, England, best known as the site of the 1487 Battle of Stoke Field, often considered the last major engagement of the Wars of the Roses.
E1809145 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: East Stoke | Statement: [Battle of East Stoke, location, East Stoke]
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: East Stoke
Triple: [Battle of East Stoke, location, East Stoke]
Generated description
East Stoke is a village in Nottinghamshire, England, best known as the site of the 1487 Battle of Stoke Field, often considered the last major engagement of the Wars of the Roses.

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_69efd6b826908190857e6e7dad74ed93 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f642d40dd081909a2cf60eeb235784 completed May 2, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15e6b50c18819099041cfd31f2a6d5 completed May 26, 2026, 6:30 p.m.
NEDg Description generation batch_6a15eec2ef9081908b5a99d7900eb82f completed May 26, 2026, 7:04 p.m.
NED2 Entity disambiguation (via description) batch_6a15f40d69c48190ab96b08d36dcd904 completed May 26, 2026, 7:27 p.m.
Created at: April 27, 2026, 10:30 p.m.