Triple

T23079488
Position Surface form Disambiguated ID Type / Status
Subject CSS Hunley E575427 entity
Predicate designer P184 FINISHED
Object James McClintock
James McClintock was a 19th-century American engineer and inventor best known for co-designing the Confederate submarine CSS Hunley, one of the first combat submarines in history.
E1598238 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: James McClintock | Statement: [CSS Hunley, designer, James McClintock]
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: James McClintock
Triple: [CSS Hunley, designer, James McClintock]
Generated description
James McClintock was a 19th-century American engineer and inventor best known for co-designing the Confederate submarine CSS Hunley, one of the first combat submarines in history.

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_69e245be28d48190ad1348d5a73db37d completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18c66a80481909ebc2ba69f1e4bd9 completed April 29, 2026, 4:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f536a6b6c8190a772c7f732718644 completed May 21, 2026, 6:48 p.m.
NEDg Description generation batch_6a0f5461406c8190a5cbf19b614ca745 completed May 21, 2026, 6:52 p.m.
NED2 Entity disambiguation (via description) batch_6a0f54e4e1d081908e4e42056ce1d23e completed May 21, 2026, 6:54 p.m.
Created at: April 17, 2026, 3:56 p.m.