Triple
T32223969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandigram Tea Estate |
E823143
|
entity |
| Predicate | isLocatedInTeaRegion |
P62960
|
FINISHED |
| Object | Assam tea region |
—
|
NE NERFINISHED |
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: Assam tea region | Statement: [Nandigram Tea Estate, isLocatedInTeaRegion, Assam tea region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInTeaRegion Context triple: [Nandigram Tea Estate, isLocatedInTeaRegion, Assam tea region]
-
A.
teaProductionRegion
chosen
Indicates the region or area where tea is produced or cultivated.
-
B.
partOfCoffeeRegion
Indicates that one entity is a subregion or component area within a larger coffee-producing region.
-
C.
cultivatedBy
Indicates that something (such as land, crops, or plants) is grown, tended, or developed through the efforts or care of a particular agent.
-
D.
cultivatedInRegion
Indicates that something (such as a crop or plant) is grown or produced through cultivation within a specified geographic region.
-
E.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 12:38 a.m.