Triple
T12136861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gediminas |
E289079
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Jaunutis |
E968146
|
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: Jaunutis | Statement: [Gediminas, child, Jaunutis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaunutis Context triple: [Gediminas, child, Jaunutis]
-
A.
Jaunutis
chosen
Jaunutis was a 14th-century Grand Duke of Lithuania, one of the sons of Gediminas, who briefly ruled before being deposed by his brothers.
-
B.
Jaunsari
Jaunsari is an Indo-Aryan language spoken by the Jaunsari people in the Jaunsar-Bawar region of northern India.
-
C.
Valtė
Valtė is a Lithuanian feminine given name, used as a diminutive or affectionate form of the name Valter.
-
D.
Naujaat
Naujaat is a small Inuit community in Nunavut, Canada, located on the Arctic coast at the north end of Roes Welcome Sound.
-
E.
Visaginas
Visaginas is a town in northeastern Lithuania known for its Soviet-era origins and proximity to the now-decommissioned Ignalina Nuclear Power Plant.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158dd00c819082651891898b91bb |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a7baee88190a32a5a3cd0b8a326 |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:49 p.m.