Triple
T14457233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leszek |
E358487
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Lestek |
E1100329
|
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: Lestek | Statement: [Leszek, relatedName, Lestek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lestek Context triple: [Leszek, relatedName, Lestek]
-
A.
Lestek
chosen
Lestek is a masculine given name of Slavic origin, historically associated with early Polish rulers.
-
B.
Leitak
Leitak is a dialectal variety of the Hakha Chin language spoken by a specific Chin community.
-
C.
Lentekhi
Lentekhi is a small mountain town in northwestern Georgia, serving as a local center in the historic Racha-Lechkhumi and Svaneti region.
-
D.
Leyhof
Leyhof is a residential neighborhood in the Dutch town of Leiderdorp, located in the province of South Holland.
-
E.
Krewo
Krewo is a historic village in present-day Belarus, best known as the site where the Union of Krewo was concluded in 1385, marking a pivotal dynastic union between the Kingdom of Poland and the Grand Duchy of Lithuania.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d890be88190afe61dde0d1e75a8 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:19 a.m.