Triple
T5503562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kisi |
E144382
|
entity |
| Predicate | currentTrend |
P39078
|
FINISHED |
| Object | increasingly popular in artisanal wines |
—
|
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: increasingly popular in artisanal wines | Statement: [Kisi, currentTrend, increasingly popular in artisanal wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentTrend Context triple: [Kisi, currentTrend, increasingly popular in artisanal wines]
-
A.
trends
chosen
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
B.
currentPoliticalTrend
Indicates the prevailing direction or pattern of political attitudes, behaviors, or power dynamics at a given time.
-
C.
socialPhenomenon
Indicates a relationship where an event, behavior, or pattern emerges from and affects interactions within a society or group.
-
D.
trendy
Indicates that something is currently fashionable, popular, or in line with prevailing styles or tastes.
-
E.
designTrend
Indicates a prevailing or emerging stylistic direction or pattern that influences how something is designed over a period of 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0bbea48190bb6fecaee9c0b1d0 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.