Triple
T24909925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | названиеНаПольском |
P15778
|
FINISHED |
| Object | Szeszupa |
—
|
NE NERFINISHED |
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: Szeszupa | Statement: [Шешупе, названиеНаПольском, Szeszupa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: названиеНаПольском Context triple: [Шешупе, названиеНаПольском, Szeszupa]
-
A.
hasNameInPolish
chosen
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
B.
officialNamePolish
Indicates the official or legally recognized name of an entity as expressed in the Polish language.
-
C.
equivalentTitleInPolish
Indicates that one entity has a title in Polish that is equivalent in meaning or status to the title of another entity.
-
D.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
-
E.
hasNameInRusyn
Indicates that an entity has a specific name or label expressed in the Rusyn language.
- F. None of above.
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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:27 a.m.