Triple
T7960338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wulfhere of Mercia |
E184846
|
entity |
| Predicate | dynasty |
P1547
|
FINISHED |
| Object | Iclingas |
E182997
|
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: Iclingas | Statement: [Wulfhere of Mercia, dynasty, Iclingas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iclingas Context triple: [Wulfhere of Mercia, dynasty, Iclingas]
-
A.
Iclingas
chosen
The Iclingas were the early royal dynasty of the Anglo-Saxon kingdom of Mercia, traditionally tracing their lineage back to the legendary figure Icel.
-
B.
Garliava
Garliava is a small town in central Lithuania known as a suburban community near the city of Kaunas.
-
C.
Ehling
Ehling is a German-language surname, likely of similar origin and meaning to the related name Ehle.
-
D.
Soligalich
Soligalich is a historic Russian town known for its preserved 18th–19th century architecture and location along the Kostroma River in Kostroma Oblast.
-
E.
Broglien
A Broglien is a resident or native of the commune of Broglie in the Eure department of northern France.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b8136448190890f007fb4fb7625 |
completed | March 31, 2026, 3:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe084d9348190b4102fbdfedca297 |
completed | March 31, 2026, 2:56 p.m. |
Created at: March 30, 2026, 5:12 p.m.