Triple
T4360313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dig for Victory campaign |
E98644
|
entity |
| Predicate | promotedCrop |
P55351
|
FINISHED |
| Object | potatoes |
—
|
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: potatoes | Statement: [Dig for Victory campaign, promotedCrop, potatoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedCrop Context triple: [Dig for Victory campaign, promotedCrop, potatoes]
-
A.
introducedCrop
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
-
B.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
notableCrop
chosen
Indicates that a particular crop is especially significant, prominent, or characteristic in relation to the referenced entity.
-
D.
crop
Indicates the action of cutting or trimming part of an object or image, typically to remove unwanted outer areas while keeping a selected region.
-
E.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e3220881909dc9d02ab024abf5 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.