Triple
T21549001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan de Limay |
E531709
|
entity |
| Predicate | regionalEconomyContext |
P65240
|
FINISHED |
| Object | part of Estelí rural economy |
—
|
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: part of Estelí rural economy | Statement: [San Juan de Limay, regionalEconomyContext, part of Estelí rural economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalEconomyContext Context triple: [San Juan de Limay, regionalEconomyContext, part of Estelí rural economy]
-
A.
regionalEconomyActivity
Indicates the type or level of economic activity occurring within a specific geographic region.
-
B.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
C.
economicImpactRegion
Indicates the region or geographic area that experiences or is affected by a particular economic impact.
-
D.
economicArea
chosen
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.
servesEconomicRegion
Indicates that an entity provides services, support, or functions that benefit or are directed toward a particular 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb590bb0881908cd849096696db10 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.