Triple
T784310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamaecyparis |
E16566
|
entity |
| Predicate | hasCultivars |
P8128
|
FINISHED |
| Object | numerous ornamental cultivars |
—
|
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: numerous ornamental cultivars | Statement: [Chamaecyparis, hasCultivars, numerous ornamental cultivars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultivars Context triple: [Chamaecyparis, hasCultivars, numerous ornamental cultivars]
-
A.
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.
-
B.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
C.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
D.
has32Varieties
Indicates that one entity possesses or includes exactly 32 distinct types, forms, or varieties of another entity.
-
E.
parentVariety
Indicates that one variety is the direct parent or source variety from which another variety is derived or developed.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a769dc6481908f12e872f997acf3 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.