Triple
T3718719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish printing |
E81589
|
entity |
| Predicate | hasImportantCenter |
P6682
|
FINISHED |
| Object | Vilna |
E271703
|
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: Vilna | Statement: [Jewish printing, hasImportantCenter, Vilna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vilna Context triple: [Jewish printing, hasImportantCenter, Vilna]
-
A.
Vilna
chosen
Vilna is the historical name for Vilnius, the capital city of Lithuania and a major cultural and political center of the region.
-
B.
Vitebsk
Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
-
C.
Novopolotsk
Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
-
D.
Kovno
Kovno is the historical name for Kaunas, a major city in Lithuania that was once part of the Russian Empire and had a significant Jewish community.
-
E.
Hrodna
Hrodna is a historic city in western Belarus known for its well-preserved architecture and role as a major cultural and economic center of the region.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca984844819087a2f6b20d2f19e7 |
completed | March 8, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4db0ba70481908dfd11ee5c89faff |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:33 p.m.