Triple
T32726992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferno (Valtellina) |
E836826
|
entity |
| Predicate | harvestConditions |
P23127
|
FINISHED |
| Object | labor-intensive due to steep terraces |
—
|
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: labor-intensive due to steep terraces | Statement: [Inferno (Valtellina), harvestConditions, labor-intensive due to steep terraces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestConditions Context triple: [Inferno (Valtellina), harvestConditions, labor-intensive due to steep terraces]
-
A.
harvestCondition
chosen
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
B.
harvestTiming
Indicates the point in time or period when a crop or resource is collected or harvested.
-
C.
isHarvestedBy
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
D.
isTypicallyHarvested
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
-
E.
isPostHarvest
Indicates that an entity or process occurs after the harvesting of a crop or resource has been completed.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b953348190bc38ddc49fdd7571 |
completed | May 3, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.