Triple
T15932822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulipa |
E386363
|
entity |
| Predicate | hasHybridCultivars |
P8128
|
FINISHED |
| Object | garden tulips |
—
|
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: garden tulips | Statement: [Tulipa, hasHybridCultivars, garden tulips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHybridCultivars Context triple: [Tulipa, hasHybridCultivars, garden tulips]
-
A.
hasHybridSpecies
Indicates that one entity is a hybrid species that results from the combination or crossbreeding of another entity (or entities).
-
B.
hasCultivar
chosen
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.
-
C.
hasHybridization
Indicates that one entity participates in or results from a hybridization process involving another entity.
-
D.
hasHybridSystem
Indicates that an entity is equipped with or incorporates a hybrid system, typically combining two or more different technologies or power sources.
-
E.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.