Triple
T8192826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betti |
E191354
|
entity |
| Predicate | shortFormOf |
P43
|
FINISHED |
| Object | Bettina |
E36497
|
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: Bettina | Statement: [Betti, shortFormOf, Bettina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bettina Context triple: [Betti, shortFormOf, Bettina]
-
A.
Bettina
chosen
Bettina is a feminine given name of Hebrew origin, often considered a diminutive of Elisabeth or Benedetta and used in various European languages.
-
B.
Dorothee
Dorothee is a feminine given name, commonly used in German- and French-speaking countries, that is a variant of the name Dorothea.
-
C.
Franziska
Franziska is a feminine given name of German origin, closely related to and cognate with the name Frances.
-
D.
Elfriede
Elfriede is a feminine given name of German origin, notably borne by Austrian Nobel Prize–winning writer Elfriede Jelinek.
-
E.
Anna Bertha Ludwig
Anna Bertha Ludwig was the wife of physicist Wilhelm Röntgen, who supported him throughout his pioneering work on X-rays.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1d7aa48190adbbce88b3bed1a3 |
completed | March 31, 2026, 5:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cceda1b22c8190acc1a2cd0fe36b70 |
completed | April 1, 2026, 10:04 a.m. |
Created at: March 30, 2026, 5:42 p.m.