Triple
T17702422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Pihkva |
E441339
|
entity |
| Predicate | hasLanguageVariantNameIn |
P115095
|
FINISHED |
| Object | Estonian |
—
|
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: Estonian | Statement: [Lake Pihkva, hasLanguageVariantNameIn, Estonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageVariantNameIn Context triple: [Lake Pihkva, hasLanguageVariantNameIn, Estonian]
-
A.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
B.
labelLanguageVariant
chosen
Indicates that one label is a language-specific variant or localized form of another label.
-
C.
hasAcronymVariantLanguage
Indicates that a language has an alternative form represented as an acronym variant.
-
D.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
E.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715c3980819094b080a871df1100 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.