Triple

T15421015
Position Surface form Disambiguated ID Type / Status
Subject Oscar Neebe E369375 entity
Predicate familyName P18 FINISHED
Object Neebe E369375 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: Neebe | Statement: [Oscar Neebe, familyName, Neebe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neebe
Context triple: [Oscar Neebe, familyName, Neebe]
  • A. Neebe chosen
    Neebe is a surname most notably associated with Oscar Neebe, an American labor activist and one of the defendants in the 1886 Haymarket affair.
  • B. Pleeth
    Pleeth is a surname most notably associated with William Pleeth, a distinguished British cellist and influential cello teacher.
  • C. Hering
    Hering is a German surname borne by various notable individuals in fields such as science, politics, and the arts.
  • D. Uhlenhorst
    Uhlenhorst is a well-to-do residential and cultural district in Hamburg, Germany, known for its waterfront location, historic villas, and proximity to the Alster lakes.
  • E. Ransohoff
    Ransohoff is a surname most notably associated with American film and television producer Martin Ransohoff.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ebe7b1081908e6b9e6e128a8d5d completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a7adb848190836fb972bc8744f1 completed May 9, 2026, 11:28 a.m.
Created at: April 10, 2026, 3:20 a.m.