Triple
T15450536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohawk First Nation community |
E370137
|
entity |
| Predicate | traditionalCropsInclude |
P1897
|
FINISHED |
| Object | corn |
—
|
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: corn | Statement: [Mohawk First Nation community, traditionalCropsInclude, corn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCropsInclude Context triple: [Mohawk First Nation community, traditionalCropsInclude, corn]
-
A.
traditionalAgriculturalProduct
Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
-
B.
majorCrop
chosen
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
D.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03efaf82c81908b464e37ce9c159a |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.