Triple

T27517784
Position Surface form Disambiguated ID Type / Status
Subject HMNZS Philomel E694622 entity
Predicate namedAfter P63 FINISHED
Object HMS Philomel
HMS Philomel was a Royal Navy Pearl-class cruiser launched in the late 19th century that later served as the namesake and predecessor to New Zealand’s naval training establishment.
E1855335 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 Philomel | Statement: [HMNZS Philomel, namedAfter, HMS Philomel]
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 Philomel
Triple: [HMNZS Philomel, namedAfter, HMS Philomel]
Generated description
HMS Philomel was a Royal Navy Pearl-class cruiser launched in the late 19th century that later served as the namesake and predecessor to New Zealand’s naval training establishment.

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_69ef538550208190aa9de8e2cb260d93 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62efda4cc8190973e1874e98c5ad5 completed May 2, 2026, 5:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25698e11f0819081c6beb009b0a110 completed June 7, 2026, 12:52 p.m.
NEDg Description generation batch_6a256e3f248c819090c3d806f3c3fd84 completed June 7, 2026, 1:12 p.m.
NED2 Entity disambiguation (via description) batch_6a2572394c84819085d3812520aeb050 completed June 7, 2026, 1:29 p.m.
Created at: April 27, 2026, 1:19 p.m.