Triple
T37378204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnokokshaysk |
E928349
|
entity |
| Predicate | hasEtymologyContains |
P124938
|
FINISHED |
| Object | Kokshaga |
—
|
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: Kokshaga | Statement: [Krasnokokshaysk, hasEtymologyContains, Kokshaga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEtymologyContains Context triple: [Krasnokokshaysk, hasEtymologyContains, Kokshaga]
-
A.
hasEtymologyConcept
Indicates that something derives its origin, form, or meaning from a particular etymological concept or source.
-
B.
hasEtymologyDetail
Indicates a relationship where additional explanatory or contextual information about the origin or derivation of a term is provided.
-
C.
hasEtymologicalBasis
chosen
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
D.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
E.
hasLatinEtymology
Indicates that something originates from or is derived from a Latin word or linguistic root.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:16 p.m.