Triple
T21908735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darjeeling tea |
E541007
|
entity |
| Predicate | grownAtAltitude |
P38307
|
FINISHED |
| Object | 600–2,000 metres |
—
|
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: 600–2,000 metres | Statement: [Darjeeling tea, grownAtAltitude, 600–2,000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grownAtAltitude Context triple: [Darjeeling tea, grownAtAltitude, 600–2,000 metres]
-
A.
grownAtHighElevation
chosen
Indicates that something is cultivated or produced in locations situated at relatively high altitudes above sea level.
-
B.
hasAlpineFlora
Indicates that an entity possesses or is characterized by plant life typical of high-altitude alpine environments.
-
C.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
D.
hasAlpineTundra
Indicates that something possesses or is characterized by an alpine tundra environment or habitat.
-
E.
higherInlandElevation
Indicates that one location has a greater elevation above sea level than another location, specifically when both are considered in an inland (away from the coast) context.
- 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.