Triple
T16552779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adalbert |
E402114
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Adelbert |
E22132
|
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: Adelbert | Statement: [Adalbert, hasVariantForm, Adelbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adelbert Context triple: [Adalbert, hasVariantForm, Adelbert]
-
A.
Adelbert
chosen
Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
-
B.
Woldemar
Woldemar is a masculine given name of Germanic origin, commonly considered a variant of Waldemar.
-
C.
Thaddaeus
Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
-
D.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
-
E.
Amelius
Amelius was a 3rd-century Neoplatonist philosopher and disciple of Plotinus, known for his extensive commentaries on Platonic thought.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc6735481908b59bbf80fb3469b |
completed | April 18, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006edbd8388190b9a96c1cc5c9119e |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:15 a.m.