Triple
T10680090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blue crele Cochin |
E251722
|
entity |
| Predicate | hasHardiness |
P1349
|
FINISHED |
| Object | cold hardy |
—
|
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: cold hardy | Statement: [blue crele Cochin, hasHardiness, cold hardy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHardiness Context triple: [blue crele Cochin, hasHardiness, cold hardy]
-
A.
hardiness
chosen
Indicates the degree to which an entity can withstand or endure harsh, adverse, or challenging conditions.
-
B.
hasPlantHardinessZone
Indicates that a location or area falls within a specified plant hardiness zone, defining the climatic conditions suitable for plant survival there.
-
C.
hasGrowthHabit
Indicates the characteristic way in which an organism typically grows or develops in form or structure.
-
D.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
E.
hasTreeVigor
Indicates the assessed strength, health, and growth potential of a tree in relation to its current condition or environment.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc03dc4819080a6211a2bfaaf0a |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.