Triple
T11977639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocos nucifera |
E285075
|
entity |
| Predicate | temperatureRequirement |
P99538
|
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: [Cocos nucifera, temperatureRequirement, frost-sensitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureRequirement Context triple: [Cocos nucifera, temperatureRequirement, frost-sensitive]
-
A.
temperatureConditions
chosen
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
B.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
E.
hasMinTemperature
Indicates that something possesses or is associated with a specified minimum temperature value.
- 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.