Triple
T9721335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luts’k |
E235479
|
entity |
| Predicate | hasAlternateName |
P39
|
FINISHED |
| Object | Luc’k |
E195375
|
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: Luc’k | Statement: [Luts’k, hasAlternateName, Luc’k]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luc’k Context triple: [Luts’k, hasAlternateName, Luc’k]
-
A.
Luki
Luki is a common diminutive or nickname for the given name Lukas.
-
B.
Lukin
Lukin is a component or module associated with the "No Code" system, likely serving as a distinct functional part within that broader platform.
-
C.
Luppi
Luppi is a surname most notably associated with Argentine actor Federico Luppi, renowned for his work in Latin American and Spanish cinema.
-
D.
Łuck
chosen
Łuck is the Polish name for Lutsk, a historic city in western Ukraine known for its medieval castle and role as a regional cultural center.
-
E.
Lukiiko
Lukiiko is the traditional legislative council of the Kingdom of Buganda, serving as its main representative and advisory assembly.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e42ce948190b52791b27c4456dc |
completed | April 1, 2026, 10:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fa130548190ae729487b90fa8a7 |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:20 p.m.