Triple
T28265457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dealu Mare wine region |
E712689
|
entity |
| Predicate | harvestPeriodCharacteristic |
P164387
|
FINISHED |
| Object | late ripening for red varieties |
—
|
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: late ripening for red varieties | Statement: [Dealu Mare wine region, harvestPeriodCharacteristic, late ripening for red varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestPeriodCharacteristic Context triple: [Dealu Mare wine region, harvestPeriodCharacteristic, late ripening for red varieties]
-
A.
harvestTiming
chosen
Indicates the point in time or period when a crop or resource is collected or harvested.
-
B.
isTypicallyHarvested
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
-
C.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
D.
harvestStyle
Indicates the manner or method by which a harvesting action is carried out.
-
E.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:14 p.m.