Triple

T36123185
Position Surface form Disambiguated ID Type / Status
Subject SS Superior City wreck E1044799 entity
Predicate originalShipName P14494 FINISHED
Object SS Superior City
SS Superior City was an early 20th-century Great Lakes freighter that tragically sank in Lake Superior and is now known for its well-preserved shipwreck.
E2169342 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: SS Superior City | Statement: [SS Superior City wreck, originalShipName, SS Superior City]
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: SS Superior City
Triple: [SS Superior City wreck, originalShipName, SS Superior City]
Generated description
SS Superior City was an early 20th-century Great Lakes freighter that tragically sank in Lake Superior and is now known for its well-preserved shipwreck.

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_69f76e356c908190abc6ca1e6a05b011 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b2f567688190b502c9c06dad37f8 completed May 3, 2026, 8:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38de0ed2f88190a8727d43bbfa9c35 completed June 22, 2026, 7:02 a.m.
NEDg Description generation batch_6a38de9a1ae88190a185a30c60e4a79d completed June 22, 2026, 7:04 a.m.
NED2 Entity disambiguation (via description) batch_6a38df04c6e881908a0ad5b6abcfe7be completed June 22, 2026, 7:06 a.m.
Created at: May 3, 2026, 4:08 p.m.