Triple
T8771813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vara |
E208480
|
entity |
| Predicate | isDiminutiveInCulture |
P456
|
FINISHED |
| Object | Slavic cultures |
—
|
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: Slavic cultures | Statement: [Vara, isDiminutiveInCulture, Slavic cultures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiminutiveInCulture Context triple: [Vara, isDiminutiveInCulture, Slavic cultures]
-
A.
hasDiminutive
chosen
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
B.
isColloquialTerm
Indicates that one term is an informal or non-standard, colloquial way of referring to another term or concept.
-
C.
usedNisba
Indicates that one entity is described or classified using a nisba (relational adjective or gentilic) derived from another entity.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2c54c08190a904723d1f0527a4 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.