Triple
T32023731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borderies (Cognac cru) |
E817761
|
entity |
| Predicate | harvest |
P148365
|
FINISHED |
| Object | hand and machine harvesting both used |
—
|
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 and machine harvesting both used | Statement: [Borderies (Cognac cru), harvest, hand and machine harvesting both used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvest Context triple: [Borderies (Cognac cru), harvest, hand and machine harvesting both used]
-
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.
harvestSource
Indicates that one entity serves as the origin or provider from which another entity obtains or collects resources, materials, or data.
-
D.
harvestFestival
Indicates a relationship where a community or group holds a celebratory event or ritual to mark and give thanks for the gathering of crops or agricultural produce.
-
E.
harvestTiming
Indicates the point in time or period when a crop or resource is collected or harvested.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4684000819090d1f2f28af40db9 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.