Triple
T15114004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guria |
E360987
|
entity |
| Predicate | teaIntroductionPeriod |
P117368
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Guria, teaIntroductionPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teaIntroductionPeriod Context triple: [Guria, teaIntroductionPeriod, late 19th century]
-
A.
teaCulture
Indicates the relationship in which practices, rituals, and social norms surrounding the preparation and consumption of tea are shared, expressed, or maintained.
-
B.
teaType
Indicates the specific variety or category of tea associated with an entity.
-
C.
teaCategory
Indicates that one item is classified as belonging to a particular category or type of tea.
-
D.
teaBrand
Indicates that one entity is a brand or producer associated with a particular type or product line of tea for the other entity.
-
E.
coffeeIntroducedBy
Indicates that a particular coffee was brought, presented, or made known to someone by a specific person or source.
- F. None of above. chosen
Provenance (4 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:05 a.m.