Triple
T27646888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nilgiri tea |
E696735
|
entity |
| Predicate | cultivarSource |
P76746
|
FINISHED |
| Object | Camellia sinensis var. sinensis |
—
|
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: Camellia sinensis var. sinensis | Statement: [Nilgiri tea, cultivarSource, Camellia sinensis var. sinensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultivarSource Context triple: [Nilgiri tea, cultivarSource, Camellia sinensis var. sinensis]
-
A.
cultivarOrigin
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
-
B.
plantSource
chosen
Indicates that something originates from, is derived from, or is produced by a particular plant.
-
C.
cultivarName
Indicates that a specific cultivated variety (cultivar) is designated by a particular name.
-
D.
exportCultivar
Indicates the action of sending a plant cultivar from one place or organization to another for use, trade, or distribution.
-
E.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63195d7808190a4d4bde80e99d31d |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:29 p.m.