Triple
T8166762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trasianka |
E190710
|
entity |
| Predicate | hasUsageTrend |
P5318
|
FINISHED |
| Object | declining among younger educated speakers |
—
|
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: declining among younger educated speakers | Statement: [Trasianka, hasUsageTrend, declining among younger educated speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageTrend Context triple: [Trasianka, hasUsageTrend, declining among younger educated speakers]
-
A.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
C.
hasOnlineTrendType
Indicates that an entity is associated with a specific category or type of online trend.
-
D.
hasTendency
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
-
E.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb46680fac81908df134df9bf84915 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.