Triple
T27907925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vallée de la Marne wine region |
E705838
|
entity |
| Predicate | harvestMethodCommon |
P148365
|
FINISHED |
| Object | hand harvesting |
—
|
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: hand harvesting | Statement: [Vallée de la Marne wine region, harvestMethodCommon, hand harvesting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestMethodCommon Context triple: [Vallée de la Marne wine region, harvestMethodCommon, hand harvesting]
-
A.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting process.
-
B.
harvestStyle
chosen
Indicates the manner or method by which a harvesting action is carried out.
-
C.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
D.
interpretsHarvestAs
Indicates that one entity understands, explains, or treats a given harvest event or result as having a particular meaning, status, or interpretation.
-
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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:47 p.m.