Triple

T17079578
Position Surface form Disambiguated ID Type / Status
Subject Garrett A. Morgan E414435 entity
Predicate familyName P18 FINISHED
Object Morgan E1067484 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: Morgan | Statement: [Garrett A. Morgan, familyName, Morgan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morgan
Context triple: [Garrett A. Morgan, familyName, Morgan]
  • A. Morgan
    Morgan is a Chicago 'L' rapid transit station on the Near West Side serving the city's Pink and Green Lines.
  • B. Morgan
    Morgan is a 2016 science fiction horror film about a genetically engineered human hybrid whose violent behavior leads to a crisis among the scientists who created her.
  • C. Morgan
    Morgan is the party that successfully defended the constitutionality of a key provision of the Voting Rights Act in the landmark U.S. Supreme Court case Katzenbach v. Morgan.
  • D. Morgan
    Morgan is a small city in northern Utah that serves as the administrative and commercial center of Morgan County.
  • E. Morgan chosen
    Morgan is a common Welsh surname with deep cultural and historical roots in Wales and among people of Welsh descent.
  • 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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbe24a6481908b4596c95220df4a completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ee243c081909aa6d470e002222a completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:34 a.m.