Triple
T21815067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picardan |
E538584
|
entity |
| Predicate | cultivationFrequency |
P113194
|
FINISHED |
| Object | very limited plantings |
—
|
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: very limited plantings | Statement: [Picardan, cultivationFrequency, very limited plantings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultivationFrequency Context triple: [Picardan, cultivationFrequency, very limited plantings]
-
A.
cultivationType
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
-
B.
cultivationScale
chosen
Indicates the relative size or extent of cultivation applied to something, such as how intensively or broadly it is being cultivated.
-
C.
cultivationRequirement
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
-
D.
methodOfCultivation
Indicates the technique or process used to grow, raise, or cultivate something (such as a crop, organism, or resource).
-
E.
cultivationChallenge
Indicates a situation where the process of cultivating or growing something faces difficulty, obstacles, or increased effort.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.