Triple
T584237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milpa Alta |
E15123
|
entity |
| Predicate | hasMajorCrop |
P1897
|
FINISHED |
| Object | nopal cactus |
—
|
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: nopal cactus | Statement: [Milpa Alta, hasMajorCrop, nopal cactus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCrop Context triple: [Milpa Alta, hasMajorCrop, nopal cactus]
-
A.
majorCrop
chosen
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
B.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
C.
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.
-
D.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
E.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b8745c88190af9672e5fe8396c3 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.