Triple
T10883718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surprise, Nebraska |
E256986
|
entity |
| Predicate | hasRegionalEconomy |
P32182
|
FINISHED |
| Object | family-owned 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: family-owned farms | Statement: [Surprise, Nebraska, hasRegionalEconomy, family-owned farms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalEconomy Context triple: [Surprise, Nebraska, hasRegionalEconomy, family-owned farms]
-
A.
regionalEconomyType
chosen
Indicates the type or classification of an economy associated with a specific region.
-
B.
hasMajorEconomicRegion
Indicates that an entity includes, is associated with, or is part of a primary or significant economic region within a larger economic or geographic context.
-
C.
isMajorEconomicAreaFor
Indicates that a location or region serves as a primary center of significant economic activity for a specified entity or sector.
-
D.
economicArea
Indicates that one entity is part of, associated with, or falls under the jurisdiction of a defined economic region or zone of another entity.
-
E.
hasNearbyEconomicRegion
Indicates that one economic region is geographically close to or adjacent to another economic region.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.