Triple
T23102462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornalin |
E576068
|
entity |
| Predicate | cultivationDifficulty |
P111368
|
FINISHED |
| Object | sensitive and low-yielding |
—
|
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: sensitive and low-yielding | Statement: [Cornalin, cultivationDifficulty, sensitive and low-yielding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultivationDifficulty Context triple: [Cornalin, cultivationDifficulty, sensitive and low-yielding]
-
A.
cultivationChallenge
chosen
Indicates a situation where the process of cultivating or growing something faces difficulty, obstacles, or increased effort.
-
B.
cultivationScale
Indicates the relative size or extent of cultivation applied to something, such as how intensively or broadly it is being cultivated.
-
C.
cultivationRequirement
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
-
D.
cultivationType
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
-
E.
cultivatedThrough
Indicates that something is developed, improved, or brought into existence by means of a specified method, practice, or process.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de9fa8c81909fd26ff37173b85b |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.