Triple

T14816347
Position Surface form Disambiguated ID Type / Status
Subject Eulalie Mackecknie Shinn E348326 entity
Predicate hasSurname P18 FINISHED
Object Shinn E611783 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: Shinn | Statement: [Eulalie Mackecknie Shinn, hasSurname, Shinn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shinn
Context triple: [Eulalie Mackecknie Shinn, hasSurname, Shinn]
  • A. Shinn chosen
    Shinn is a surname most notably associated with Everett Shinn, an American realist painter and member of the Ashcan School.
  • B. Shin
    Shin is a common Japanese given name element that often conveys meanings like “truth,” “new,” or “heart,” depending on the kanji used.
  • C. Shin
    Shin is a fictional character voiced by American actress and singer Ashley Johnson, known for her versatile roles in animation and video games.
  • D. Shin
    Shin is the ethnonym for the Shina people, an Indo-Aryan ethnic group primarily inhabiting the Gilgit-Baltistan region of northern Pakistan and surrounding areas.
  • E. Shinasha
    Shinasha is a North Omotic language spoken by the Shinasha people of western Ethiopia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decfe2c1ec81908b3dff7a5d0e85d0 completed April 14, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe3897691c819085ef89480e730723 completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:49 a.m.