Triple
T26372625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey Royal potatoes |
E660811
|
entity |
| Predicate | harvestedIn |
P138035
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Jersey Royal potatoes, harvestedIn, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestedIn Context triple: [Jersey Royal potatoes, harvestedIn, spring]
-
A.
isHarvestedBy
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
B.
isTypicallyHarvested
chosen
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
-
C.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting process.
-
D.
harvestSize
Indicates the quantity or scale of yield obtained from a harvesting activity.
-
E.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f610310d7c8190a14a7f7aa377846a |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:59 p.m.