Triple
T609218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Belt |
E12059
|
entity |
| Predicate | typicalFarmSize |
P3664
|
FINISHED |
| Object | large commercial farms |
—
|
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: large commercial farms | Statement: [Corn Belt, typicalFarmSize, large commercial farms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFarmSize Context triple: [Corn Belt, typicalFarmSize, large commercial farms]
-
A.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
-
B.
agriculturalRole
Indicates a role or function that an entity has within agricultural activities, production, or systems.
-
C.
requiredShareOfLand
Indicates the proportion or amount of land that must be allocated or possessed to satisfy a specified requirement or rule.
-
D.
typicalUnitSize
chosen
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
E.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df54eec8190af3f5f04c01d5d2a |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.