Triple
T19649945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norberto |
E471782
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Norbert |
—
|
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: Norbert | Statement: [Norberto, hasVariant, Norbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Norbert Context triple: [Norberto, hasVariant, 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.
Benno
Benno is a masculine given name, used as a variant or extended form of the name Ben in various European languages.
-
D.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
E.
Adelbert
Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641286bbc8190886f309de13063bf |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.