Triple

T24108687
Position Surface form Disambiguated ID Type / Status
Subject Henry A. Walke E597298 entity
Predicate shipCommanded P884 FINISHED
Object USS Vicksburg
USS Vicksburg was a United States Navy warship that served during the American Civil War, participating in riverine and coastal operations against Confederate forces.
E1735228 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: USS Vicksburg | Statement: [Henry A. Walke, shipCommanded, USS Vicksburg]
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: USS Vicksburg
Triple: [Henry A. Walke, shipCommanded, USS Vicksburg]
Generated description
USS Vicksburg was a United States Navy warship that served during the American Civil War, participating in riverine and coastal operations against Confederate forces.

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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de19057c819096a8b3290d33e2f6 completed April 29, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11ebe4801c8190a22526d402b01e5d completed May 23, 2026, 6:03 p.m.
NEDg Description generation batch_6a11ee266f008190843eb2ee53a4c734 completed May 23, 2026, 6:12 p.m.
NED2 Entity disambiguation (via description) batch_6a11ee9c89dc8190aaa61318e8210888 completed May 23, 2026, 6:14 p.m.
Created at: April 17, 2026, 11:02 p.m.