Triple
T2593671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Woodlands |
E58180
|
entity |
| Predicate | agriculturalStaple |
P1897
|
FINISHED |
| Object | maize |
—
|
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: maize | Statement: [Southeastern Woodlands, agriculturalStaple, maize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalStaple Context triple: [Southeastern Woodlands, agriculturalStaple, maize]
-
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.
traditionalAgriculturalProduct
Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
E.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd426e2d4819081a07920b4d2a1cc |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.