Triple
T2361136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bärbel |
E47273
|
entity |
| Predicate | hasRelatedName |
P3889
|
FINISHED |
| Object | Bärbele |
E47273
|
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: Bärbele | Statement: [Bärbel, hasRelatedName, Bärbele]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bärbele Context triple: [Bärbel, hasRelatedName, Bärbele]
-
A.
Baerbel
Baerbel is a feminine given name of German origin, commonly used as an alternative spelling of Bärbel.
-
B.
Bärbel
chosen
Bärbel is a German feminine given name, commonly used as a diminutive or variant of Barbara.
-
C.
Bettina
Bettina is a feminine given name of Hebrew origin, often considered a diminutive of Elisabeth or Benedetta and used in various European languages.
-
D.
Dorothee
Dorothee is a feminine given name, commonly used in German- and French-speaking countries, that is a variant of the name Dorothea.
-
E.
Gisela
Gisela was a daughter of Charlemagne, the Frankish king and first Holy Roman Emperor, and a member of the Carolingian royal family.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc723c66481908a9b94991f651b3b |
completed | March 7, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef0913e748190bbb5c54b86b415bd |
completed | March 9, 2026, 4:08 p.m. |
Created at: March 4, 2026, 7:55 p.m.