Triple
T12909815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian dynasty |
E308824
|
entity |
| Predicate | hasMonarch |
P765
|
FINISHED |
| Object | Cunincpert |
E1010472
|
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: Cunincpert | Statement: [Bavarian dynasty, hasMonarch, Cunincpert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cunincpert Context triple: [Bavarian dynasty, hasMonarch, Cunincpert]
-
A.
Cunincpert
chosen
Cunincpert was a 7th-century King of the Lombards known for consolidating royal authority in Italy and supporting the Catholic Church.
-
B.
Theudigisel
Theudigisel was a 6th-century Visigothic king of Hispania and Septimania whose short and turbulent reign was marked by military conflict and internal instability.
-
C.
Gundemar
Gundemar was a 7th-century Visigothic king of Hispania and Septimania who ruled briefly before being succeeded by Sisebut.
-
D.
Tacenwit
Tacenwit is an alternative name for the Shenwa language, a Zenati Berber language spoken in northern Algeria.
-
E.
Reginherus
Reginherus is a Germanic personal name, historically related to and cognate with the legendary Norse name Ragnar.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719e584c81909be1ac1366effca0 |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8d101e08190b31d6aaaecf96507 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:41 p.m.