Triple
T3584494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans |
E75878
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hanns |
E75878
|
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: Hanns | Statement: [Hans, hasVariant, Hanns]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanns Context triple: [Hans, hasVariant, Hanns]
-
A.
Hans-Jürgen
Hans-Jürgen is a masculine German given name, typically used as a compound first name combining "Hans" and "Jürgen."
-
B.
Helmut
Helmut is a masculine given name of German origin, historically common in German-speaking countries.
-
C.
Hanno Hahn
Hanno Hahn was a German art historian and son of Nobel Prize–winning chemist Otto Hahn, known for his work on Renaissance and Baroque architecture before his early death in a car accident.
-
D.
Georg-Hans
Georg-Hans is the given name of Georg-Hans Reinhardt, a German general who served in the Wehrmacht during World War II.
-
E.
Hans
chosen
Hans is a masculine given name of Germanic origin commonly used in Germanic and Scandinavian countries.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc10f9b508190bde4a4e4711dd452 |
completed | March 8, 2026, 6:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b402f7ee6481908d06db05f9c09faf |
completed | March 13, 2026, 12:28 p.m. |
Created at: March 8, 2026, 3:21 p.m.