Triple
T34224162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanqueray |
E878001
|
entity |
| Predicate | keyBotanical |
P178549
|
FINISHED |
| Object | juniper |
—
|
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: juniper | Statement: [Tanqueray, keyBotanical, juniper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyBotanical Context triple: [Tanqueray, keyBotanical, juniper]
-
A.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
B.
botanicalSpecialization
Indicates a relationship where an entity is specialized or focused specifically on botany or botanical subjects.
-
C.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
D.
roleInBotany
Indicates that one entity has a specific function, position, or significance within the field or context of botany in relation to another entity.
-
E.
standardFormInBotany
Indicates that something is expressed or recorded using the conventional, officially accepted format used in botanical nomenclature or documentation.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.