Triple
T11977736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ananas comosus |
E285077
|
entity |
| Predicate | frostTolerance |
P1349
|
FINISHED |
| Object | frost-sensitive |
—
|
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: frost-sensitive | Statement: [Ananas comosus, frostTolerance, frost-sensitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frostTolerance Context triple: [Ananas comosus, frostTolerance, frost-sensitive]
-
A.
hasPlantHardinessZone
Indicates that a location or area falls within a specified plant hardiness zone, defining the climatic conditions suitable for plant survival there.
-
B.
droughtTolerance
Indicates the degree to which an entity can maintain normal function and survival under conditions of limited water availability.
-
C.
hardiness
chosen
Indicates the degree to which an entity can withstand or endure harsh, adverse, or challenging conditions.
-
D.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
E.
growsOn
Indicates that one entity develops or increases in size, number, or extent while being physically supported by or attached to 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.