Triple

T37078649
Position Surface form Disambiguated ID Type / Status
Subject Fort Harrison E917783 entity
Predicate alsoKnownAs P39 FINISHED
Object Fort Burnham
Fort Burnham was a key Confederate defensive fortification near Richmond, Virginia, that became the site of a major Civil War battle and was later renamed after Union General Hiram Burnham.
E2213141 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: Fort Burnham | Statement: [Fort Harrison, alsoKnownAs, Fort Burnham]
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: Fort Burnham
Triple: [Fort Harrison, alsoKnownAs, Fort Burnham]
Generated description
Fort Burnham was a key Confederate defensive fortification near Richmond, Virginia, that became the site of a major Civil War battle and was later renamed after Union General Hiram Burnham.

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_69f76e9771e08190a690834e3cd20654 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb2faf6bd48190a2b43e591687986d completed May 6, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3efdc2c1488190b1e8e429ca86efad completed June 26, 2026, 10:31 p.m.
NEDg Description generation batch_6a3f4662656c819083aaa555ad8c2ace completed June 27, 2026, 3:41 a.m.
NED2 Entity disambiguation (via description) batch_6a3f4822f27c8190bfd6a9d7d1a5d604 completed June 27, 2026, 3:48 a.m.
Created at: May 3, 2026, 4:14 p.m.