Triple

T33088485
Position Surface form Disambiguated ID Type / Status
Subject Raid on Yarmouth (1914) E846707 entity
Predicate shipInvolvedDefender P862 FINISHED
Object HMS Lively
HMS Lively was a Royal Navy destroyer that served during the early years of World War I, participating in North Sea operations against German naval forces.
E2049042 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 Lively | Statement: [Raid on Yarmouth (1914), shipInvolvedDefender, HMS Lively]
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 Lively
Triple: [Raid on Yarmouth (1914), shipInvolvedDefender, HMS Lively]
Generated description
HMS Lively was a Royal Navy destroyer that served during the early years of World War I, participating in North Sea operations against German naval 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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6de0ee2308190a9fa3e8b54490e29 completed May 3, 2026, 5:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3576cda614819084075e7fc1e0265b completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a35775669d481909b902b1206bac810 completed June 19, 2026, 5:07 p.m.
NED2 Entity disambiguation (via description) batch_6a3577c128948190b5690c8ff15ecde1 completed June 19, 2026, 5:09 p.m.
Created at: May 1, 2026, 1:26 a.m.