Triple
T29448542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batata-doce de Aljezur |
E746916
|
entity |
| Predicate | hasCultivationConditions |
P32783
|
FINISHED |
| Object | solos arenosos |
—
|
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: solos arenosos | Statement: [Batata-doce de Aljezur, hasCultivationConditions, solos arenosos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultivationConditions Context triple: [Batata-doce de Aljezur, hasCultivationConditions, solos arenosos]
-
A.
cultivationRequirement
chosen
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
-
B.
mayCultivate
Indicates that one entity is permitted or allowed to cultivate, grow, or farm another entity.
-
C.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
-
D.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
E.
cultivationType
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 28, 2026, 3:30 p.m.