Triple

T32289040
Position Surface form Disambiguated ID Type / Status
Subject The Queen’s York Rangers (1st American Regiment) E824913 entity
Predicate battleHonour P12198 FINISHED
Object Lexington
Lexington is a historic Massachusetts town best known as the site of the opening battle of the American Revolutionary War in 1775.
E766 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: Lexington | Statement: [The Queen’s York Rangers (1st American Regiment), battleHonour, Lexington]
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: Lexington
Triple: [The Queen’s York Rangers (1st American Regiment), battleHonour, Lexington]
Generated description
Lexington is a historic Massachusetts town best known as the site of the opening battle of the American Revolutionary War in 1775.

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_69f349101b788190b4f14884dc7d1ed2 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bd31dc488190aac7229e92312390 completed May 3, 2026, 3:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a344ef8ef5081909e54cce0e325ac27 completed June 18, 2026, 8:03 p.m.
NEDg Description generation batch_6a3450881fb881909e29256da7732066 completed June 18, 2026, 8:09 p.m.
NED2 Entity disambiguation (via description) batch_6a345466f7bc8190a3b4b5ef7d19cbee completed June 18, 2026, 8:26 p.m.
Created at: May 1, 2026, 12:44 a.m.