Triple
T3584493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans |
E75878
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hannes |
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: Hannes | Statement: [Hans, hasVariant, Hannes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hannes Context triple: [Hans, hasVariant, Hannes]
-
A.
Hans
chosen
Hans is a masculine given name of Germanic origin commonly used in Germanic and Scandinavian countries.
-
B.
Sven
Sven is the lovable reindeer companion in Disney's animated film "Frozen," known for his close bond with Kristoff and his expressive, dog-like personality.
-
C.
Johan
Johan is the given first name of J. Erik Jonsson, an American businessman and philanthropist who co-founded Texas Instruments and served as mayor of Dallas.
-
D.
Niklas
Niklas is a masculine given name commonly used in Germanic and Scandinavian countries, derived from the Greek name Nikolaos.
-
E.
Helmut
Helmut is a masculine given name of German origin, historically common in German-speaking 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_69b4c37c68108190ada8c319e1ec09fa |
completed | March 14, 2026, 2:10 a.m. |
Created at: March 8, 2026, 3:21 p.m.