Triple
T27940034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntur chili |
E700715
|
entity |
| Predicate | harvestedAs |
P138035
|
FINISHED |
| Object | ripe red fruit |
—
|
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: ripe red fruit | Statement: [Guntur chili, harvestedAs, ripe red fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestedAs Context triple: [Guntur chili, harvestedAs, ripe red fruit]
-
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.
interpretsHarvestAs
Indicates that one entity understands, explains, or treats a given harvest event or result as having a particular meaning, status, or interpretation.
-
C.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting process.
-
D.
isTypicallyHarvested
chosen
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
-
E.
harvestStyle
Indicates the manner or method by which a harvesting action is 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:17 p.m.