Triple
T19959776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidalia onion |
E479780
|
entity |
| Predicate | isTypicallyHarvested |
P138035
|
FINISHED |
| Object | April |
—
|
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: April | Statement: [Vidalia onion, isTypicallyHarvested, April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyHarvested Context triple: [Vidalia onion, isTypicallyHarvested, April]
-
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.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
-
E.
interpretsHarvestAs
Indicates that one entity understands, explains, or treats a given harvest event or result as having a particular meaning, status, or interpretation.
- F. None of above. chosen
Provenance (4 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af386548190aefac1e40aac403d |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.