Triple

T8982510
Position Surface form Disambiguated ID Type / Status
Subject Norbert Goeneutte E214566 entity
Predicate givenName P17 FINISHED
Object Norbert E158215 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: Norbert | Statement: [Norbert Goeneutte, givenName, Norbert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Norbert
Context triple: [Norbert Goeneutte, givenName, Norbert]
  • A. Norbert chosen
    Norbert is a masculine given name of Germanic origin, notably borne by the influential American mathematician and cybernetics pioneer Norbert Wiener.
  • B. Norbertus
    Norbertus is a Latinized form of the given name Norbert, historically used in ecclesiastical and scholarly contexts.
  • C. Erwin
    Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
  • D. Adelbert
    Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
  • E. Alois
    Alois is a masculine given name of Germanic origin, notably borne by Alois Hitler, the father of Adolf Hitler.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a891e881909e4b84ed82491651 completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd0b3ce0c81908a7b4297e0867cc9 completed April 3, 2026, 2:37 p.m.
Created at: March 30, 2026, 7:03 p.m.