Triple
T29448544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batata-doce de Aljezur |
E746916
|
entity |
| Predicate | hasCultivationMethod |
P143154
|
FINISHED |
| Object | agricultura tradicional |
—
|
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: agricultura tradicional | Statement: [Batata-doce de Aljezur, hasCultivationMethod, agricultura tradicional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultivationMethod Context triple: [Batata-doce de Aljezur, hasCultivationMethod, agricultura tradicional]
-
A.
methodOfCultivation
chosen
Indicates the technique or process used to grow, raise, or cultivate something (such as a crop, organism, or resource).
-
B.
cultivationType
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
cultivatedThrough
Indicates that something is developed, improved, or brought into existence by means of a specified method, practice, or process.
-
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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 3:30 p.m.