Triple

T20744564
Position Surface form Disambiguated ID Type / Status
Subject Dylan Moran E510543 entity
Predicate familyName P18 FINISHED
Object Moran NE NERFINISHED

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: Moran | Statement: [Dylan Moran, familyName, Moran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moran
Context triple: [Dylan Moran, familyName, Moran]
  • A. Moran chosen
    Moran is a surname most prominently associated with American jazz pianist and composer Jason Moran.
  • B. Moran
    Moran is a town in the Indian state of Assam, known historically as a regional commercial and cultural center in the Upper Assam area.
  • C. Moran Mor
    Moran Mor is a Syriac Christian honorific prefix traditionally used for high-ranking bishops and patriarchs, particularly within the Syriac Orthodox and related Eastern churches.
  • D. Bugs Moran
    Bugs Moran was a notorious American gangster and bootlegger in Chicago during the Prohibition era, best known as a rival of Al Capone and a target of the St. Valentine’s Day Massacre.
  • E. Dugan
    Dugan is a surname and given name of Irish origin, commonly used in English-speaking countries.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c21197088190951a4c4a7e765891 completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:33 p.m.