Triple
T17030081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giselbert |
E413169
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Gislebert |
E413169
|
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: Gislebert | Statement: [Giselbert, hasVariant, Gislebert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gislebert Context triple: [Giselbert, hasVariant, Gislebert]
-
A.
Gislebertus
Gislebertus was a 12th-century Romanesque sculptor renowned for his expressive and dramatic stone carvings, particularly at the Cathedral of Saint-Lazare in Autun, France.
-
B.
Giselbert
chosen
Giselbert is a Germanic given name of medieval origin that later evolved into the name Gilbert.
-
C.
Gisbert
Gisbert is a masculine given name of Germanic origin, closely related to Gilbert and used primarily in German- and Spanish-speaking countries.
-
D.
Galfridus
Galfridus is a masculine given name of Latin origin, historically used in medieval Europe and related to names like Geoffrey.
-
E.
Angilbert
Angilbert was a Frankish nobleman, poet, and churchman who served as a close advisor to Charlemagne and later became abbot of the monastery of Saint-Riquier.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d918ec8190b54c40c2a5e9b6b9 |
completed | April 18, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b553c588190b46785b85142dce5 |
completed | May 10, 2026, 11:57 p.m. |
Created at: April 10, 2026, 5:33 a.m.