Triple
T841305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georges |
E18182
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Georg |
E56084
|
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: Georg | Statement: [Georges, hasVariant, Georg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Georg Context triple: [Georges, hasVariant, Georg]
-
A.
Georg
chosen
Georg is the given first name of the renowned German mathematician Bernhard Riemann.
-
B.
Gerhard
Gerhard is a masculine given name of German origin, historically common in German-speaking countries.
-
C.
Georgy
Georgy is a masculine given name of Russian origin, notably borne by Soviet military commander Georgy Zhukov.
-
D.
Ludwig
Ludwig is a masculine given name of Germanic origin, historically associated with nobility and rulers and used in various forms across many European languages.
-
E.
Georges
Georges is a masculine given name of Greek origin, commonly used in French-speaking countries and derived from the name George, meaning "farmer" or "earthworker."
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe6f0dc8190a1bebb5e21f4ceac |
completed | March 1, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7a3bb2fa08190b1e8f26ceb04b08c |
completed | March 4, 2026, 3:15 a.m. |
Created at: March 1, 2026, 7:38 p.m.