Triple
T23334984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krokos Kozanis saffron |
E591552
|
entity |
| Predicate | harvestingProcess |
P148365
|
FINISHED |
| Object | manual picking of flowers |
—
|
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: manual picking of flowers | Statement: [Krokos Kozanis saffron, harvestingProcess, manual picking of flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestingProcess Context triple: [Krokos Kozanis saffron, harvestingProcess, manual picking of flowers]
-
A.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting process.
-
B.
isHarvestedBy
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
C.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
D.
harvestStyle
chosen
Indicates the manner or method by which a harvesting action is carried out.
-
E.
isTypicallyHarvested
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f08fe481908766e674164d6d45 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.