Triple
T37430224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicante Bouschet |
E930112
|
entity |
| Predicate | harvestTimeRelative |
P72820
|
FINISHED |
| Object | mid to late ripening |
—
|
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: mid to late ripening | Statement: [Alicante Bouschet, harvestTimeRelative, mid to late ripening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestTimeRelative Context triple: [Alicante Bouschet, harvestTimeRelative, mid to late ripening]
-
A.
harvestTiming
Indicates the point in time or period when a crop or resource is collected or harvested.
-
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.
ripeningTimeRelative
chosen
Indicates the temporal relationship between this entity’s ripening period and a reference ripening period (e.g., earlier, later, or at the same time).
-
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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.