Triple
T21909034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darjeeling tea GI |
E541013
|
entity |
| Predicate | linkedProduct |
P62838
|
FINISHED |
| Object | black tea from Darjeeling |
—
|
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: black tea from Darjeeling | Statement: [Darjeeling tea GI, linkedProduct, black tea from Darjeeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedProduct Context triple: [Darjeeling tea GI, linkedProduct, black tea from Darjeeling]
-
A.
relatedToProduct
chosen
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
B.
linkedProgram
Indicates that one program is associated or connected to another program in a meaningful or dependent way.
-
C.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
-
D.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
E.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d8c3108190a178ec6b3857da3f |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:39 p.m.