Triple

T8842934
Position Surface form Disambiguated ID Type / Status
Subject Jason Moran E210431 entity
Predicate familyName P18 FINISHED
Object Moran E210431 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: Moran | Statement: [Jason Moran, familyName, Moran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moran
Context triple: [Jason 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. 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.
  • D. Moneague
    Moneague is a rural village in Jamaica known for its karst landscape, seasonal lake, and location along the main road through Saint Ann Parish.
  • E. Callaghan
    Callaghan is a surname of Irish origin borne by numerous notable individuals in politics, sports, and the arts.
  • 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_69ca838967bc8190b46c3c80a2887ea4 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc608946cc8190bed3c340ba303b9c completed April 1, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf89a41a2c8190b69e5a1b157f9325 completed April 3, 2026, 9:34 a.m.
Created at: March 30, 2026, 6:48 p.m.