Triple

T36657542
Position Surface form Disambiguated ID Type / Status
Subject Admiral Sir Charles Rowley E905033 entity
Predicate notableCommand P2333 FINISHED
Object HMS Unite
HMS Unite was a Royal Navy warship of the early 19th century, known for its active service during the Napoleonic Wars and later commands by distinguished officers.
E2283070 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: HMS Unite | Statement: [Admiral Sir Charles Rowley, notableCommand, HMS Unite]
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: HMS Unite
Triple: [Admiral Sir Charles Rowley, notableCommand, HMS Unite]
Generated description
HMS Unite was a Royal Navy warship of the early 19th century, known for its active service during the Napoleonic Wars and later commands by distinguished officers.

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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c77907808190904959e4326fed7d completed May 3, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a423f6ac1b88190b0511ed1975833f6 completed June 29, 2026, 9:48 a.m.
NEDg Description generation batch_6a4241792ff881909dc373fe4c36f2de completed June 29, 2026, 9:57 a.m.
NED2 Entity disambiguation (via description) batch_6a4241ec4a908190b45997d353671445 completed June 29, 2026, 9:59 a.m.
Created at: May 3, 2026, 4:11 p.m.