Triple

T20290753
Position Surface form Disambiguated ID Type / Status
Subject Joey Meyer E510012 entity
Predicate familyName P18 FINISHED
Object Meyer 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: Meyer | Statement: [Joey Meyer, familyName, Meyer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meyer
Context triple: [Joey Meyer, familyName, Meyer]
  • A. Meyer chosen
    Meyer is a common German-origin surname borne by numerous notable individuals across fields such as literature, entertainment, sports, and academia.
  • B. Meyer
    Meyer is a given name most famously associated with Meyer Lansky, a major organized crime figure in the United States during the 20th century.
  • C. Meier
    Meier is a common German surname borne by numerous individuals across various professions and regions.
  • D. Meyerhof
    Meyerhof is a surname of German origin, notably borne by biochemist Otto Fritz Meyerhof, a Nobel laureate recognized for his work on muscle metabolism.
  • E. Mayer
    Mayer is a common German-origin surname borne by numerous notable individuals across fields such as music, science, and politics.
  • 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_69e0b4c652388190b782cad965e5a098 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67695d4d48190b932317d37aa95d9 completed April 20, 2026, 6:55 p.m.
Created at: April 16, 2026, 11:12 a.m.