Triple

T3187276
Position Surface form Disambiguated ID Type / Status
Subject Samuel Morse E66728 entity
Predicate familyName P18 FINISHED
Object Morse
Morse is a surname most famously associated with Samuel Morse, the American inventor and co-developer of the Morse code communication system.
 E334941 NE FINISHED

How this triple was built (4 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: Morse | Statement: [Samuel Morse, familyName, Morse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Morse
Context triple: [Samuel Morse, familyName, Morse]
  • A. Morse
    Morse is the middle name of Mary Baker Eddy, the founder of Christian Science.
  • B. Morse code
    Morse code is a system of encoding text characters as sequences of short and long signals (dots and dashes) used historically for long-distance telegraph and radio communication.
  • C. Pitman shorthand
    Pitman shorthand is a phonetic writing system developed in the 19th century by Isaac Pitman to enable rapid transcription of spoken English using simplified strokes and symbols.
  • D. Polybus
    Polybus is a minor figure in Greek mythology known primarily as the father of Eurymachus, one of the leading suitors of Penelope in Homer's Odyssey.
  • E. Polybus
    Polybus is the king of Corinth in Greek mythology who raises Oedipus as his own son.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Morse
Triple: [Samuel Morse, familyName, Morse]
Generated description
Morse is a surname most famously associated with Samuel Morse, the American inventor and co-developer of the Morse code communication system.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Morse
Target entity description: Morse is a surname most famously associated with Samuel Morse, the American inventor and co-developer of the Morse code communication system.
  • A. Morse
    Morse is the middle name of Mary Baker Eddy, the founder of Christian Science.
  • B. Morse code
    Morse code is a system of encoding text characters as sequences of short and long signals (dots and dashes) used historically for long-distance telegraph and radio communication.
  • C. Pitman shorthand
    Pitman shorthand is a phonetic writing system developed in the 19th century by Isaac Pitman to enable rapid transcription of spoken English using simplified strokes and symbols.
  • D. Polybus
    Polybus is a minor figure in Greek mythology known primarily as the father of Eurymachus, one of the leading suitors of Penelope in Homer's Odyssey.
  • E. Polybus
    Polybus is the king of Corinth in Greek mythology who raises Oedipus as his own son.
  • F. None of above. chosen

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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6e279288190843837751e852c9e completed March 8, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69b24b8285388190bc47264bd1028ab3 completed March 12, 2026, 5:13 a.m.
NEDg Description generation batch_69b24c9f4488819096b33baa4f35deaa completed March 12, 2026, 5:18 a.m.
NED2 Entity disambiguation (via description) batch_69b24d4f4b1c819094d2073c9889fecf completed March 12, 2026, 5:21 a.m.
Created at: March 8, 2026, 3:06 p.m.