Triple

T3023252
Position Surface form Disambiguated ID Type / Status
Subject Newman E82513 entity
Predicate hasVariant P455 FINISHED
Object Newmann E280210 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: Newmann | Statement: [Newman, hasVariant, Newmann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newmann
Context triple: [Newman, hasVariant, Newmann]
  • A. Newman chosen
    Newman is a remote mining town in Western Australia known primarily for its large iron ore operations and role as a major hub in the Pilbara region.
  • B. Newman
    Newman is a common English surname borne by numerous notable figures across fields such as film, music, politics, and academia.
  • C. Furthman
    Furthman is a surname most notably associated with American screenwriter Jules Furthman, known for his work on classic Hollywood films.
  • D. Emil Newman
    Emil Newman was an American film composer and conductor, part of the renowned Newman family of Hollywood film scorers.
  • E. Norbert
    Norbert is a masculine given name of Germanic origin, notably borne by the influential American mathematician and cybernetics pioneer Norbert Wiener.
  • 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_69ad8b1fb34081908c1b873e2b7273e1 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9ab8e0a48190ac79e674abd181cf completed March 8, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1deafdcb881908174331d5bfc6349 completed March 11, 2026, 9:29 p.m.
Created at: March 8, 2026, 3 p.m.