Triple
T24660626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veps language |
E610528
|
entity |
| Predicate | exonymOf |
P4705
|
FINISHED |
| Object | vepsän kel’ |
—
|
LITERAL 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: vepsän kel’ | Statement: [Veps language, exonymOf, vepsän kel’]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exonymOf Context triple: [Veps language, exonymOf, vepsän kel’]
-
A.
hasExonym
chosen
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
C.
hasDemonym
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
D.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
E.
hasDemonymLanguage
Indicates that a language is used as the demonym (people’s name or adjective of nationality) for inhabitants of a particular place or group.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.