Triple
T13831365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviation American Gin |
E332406
|
entity |
| Predicate | botanical |
P21608
|
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: [Aviation American Gin, botanical, juniper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: botanical Context triple: [Aviation American Gin, botanical, juniper]
-
A.
botanicalSpecialization
Indicates a relationship where an entity is specialized or focused specifically on botany or botanical subjects.
-
B.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
C.
plant
Indicates that an entity places or sets something firmly in or on a location, often so it will grow, remain fixed, or be established there.
-
D.
hasBotanicalResource
chosen
Indicates that an entity possesses, contains, or is associated with a plant-based resource (such as plants, plant parts, or botanical materials) used for some purpose.
-
E.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0299334481908c2b271eaf06e4b7 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.